Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release 3.2.0 #852

Merged
merged 10 commits into from
Oct 17, 2023
Merged

Release 3.2.0 #852

merged 10 commits into from
Oct 17, 2023

Commits on Oct 17, 2023

  1. chore: bump rocksdb up to 0.21 (#840) 

    ## Description

The `rocksdb` crate has been updated up to 0.21 in the nearcore
1.36.0-rc.1.
    @aleksuss
    aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    b425347 View commit details
    Browse the repository at this point in the history

  2. chore: fix typo (#842)

    @i-fix-typos @aleksuss
    i-fix-typos authored and aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    f9dfbe2 View commit details
    Browse the repository at this point in the history

  3. Feat: Change codeowners (#843) 

    ## Description

Code owners is pretty outdated. It's updated.
    @mrLSD @aleksuss
    mrLSD authored and aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    e97721b View commit details
    Browse the repository at this point in the history

  4. Feat: Allow hashchain to be initialized with new directly (#846) 

    ## Description

For the mainnet Aurora Engine we must use the `pause_contract` +
`start_hashchain` migration procedure because it is already live.
However, for new silos it will be useful to have the hashchain enabled
from the start. This PR adds a new optional parameter to the `new`
function where an initial (genesis) hashchain value can be specified and
then hashchain will be enabled on all transactions going forward.

## Performance / NEAR gas cost considerations

N/A; impacts `new` only.

## Testing

Tests updated to use `new` for starting the hashchain by default. Some
tests still use the migration procedure to ensure that is also tested.
    @birchmd @aleksuss
    birchmd authored and aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    0496335 View commit details
    Browse the repository at this point in the history

  5. build(deps): bump get-func-name from 2.0.0 to 2.0.2 in /etc/eth-contr… 

    …acts (#841)

Bumps [get-func-name](https://github.com/chaijs/get-func-name) from
2.0.0 to 2.0.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/chaijs/get-func-name/releases">get-func-name's
releases</a>.</em></p>
<blockquote>
<h2>v2.0.2</h2>
<h2>What's Changed</h2>
<p>Revert previous changes that shipped this as an ES module.</p>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/chaijs/get-func-name/commits/v2.0.2">https://github.com/chaijs/get-func-name/commits/v2.0.2</a></p>
<h2>v2.0.1</h2>
<h2>What's Changed</h2>
<p>Fix <a
href="https://github.com/chaijs/get-func-name/security/advisories/GHSA-4q6p-r6v2-jvc5">https://github.com/chaijs/get-func-name/security/advisories/GHSA-4q6p-r6v2-jvc5</a></p>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/chaijs/get-func-name/commits/v2.0.1">https://github.com/chaijs/get-func-name/commits/v2.0.1</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/chaijs/get-func-name/commits/v2.0.2">compare
view</a></li>
</ul>
</details>
<details>
<summary>Maintainer changes</summary>
<p>This version was pushed to npm by <a
href="https://www.npmjs.com/~keithamus">keithamus</a>, a new releaser
for get-func-name since your current version.</p>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=get-func-name&package-manager=npm_and_yarn&previous-version=2.0.0&new-version=2.0.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/aurora-is-near/aurora-engine/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Oleksandr Anyshchenko <oleksandr.anyshchenko@aurora.dev>
    @dependabot @aleksuss
    dependabot[bot] and aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    f23a5e9 View commit details
    Browse the repository at this point in the history

  6. feat: add possibility to use fixed gas cost (silo) (#746) 

    ## Description

The PR adds the possibility to set fixed gas costs per EVM transaction.
The feature could be switched on by calling the transaction
`set_fixed_gas_cost`. Also, four types of white lists have been added
for applying restrictions to deploy code and submit transactions.

**Additions**: The PR introduces a new feature: `ext-connector`, and two
additional profiles: `mainnet-silo` and `testnet-silo`. The smart
contract built with one of these profiles implies the usage of an
external eth-connector.

## Performance / NEAR gas cost considerations

There are insignificant gas cost increases. That is because we read from
the storage fixed gas cost in the execution of the `submit` method.

## Testing

The unit and integration tests which test the new logic have been added.

## How should this be reviewed

<!--
Include any recommendations of areas to be careful of to ensure that the
reviewers use extra attention.
-->

## Additional information

<!--
Include any additional information which you think should be in this PR,
such
as prior arts, future extensions, unresolved problems, or a TODO list
which
should be followed up.
-->

---------

Co-authored-by: Karim <karim@aurora.dev>
Co-authored-by: Joshua J. Bouw <joshua@aurora.dev>
Co-authored-by: Evgeny Ukhanov <evgeny@aurora.dev>
Co-authored-by: Michael Birch <michael.birch@aurora.dev>
    @aleksuss @karim-en
    @joshuajbouw @mrLSD @birchmd
    5 people committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    f10866c View commit details
    Browse the repository at this point in the history

  7. README.md grammar and formatting updates (#833) 

    <!--
Thanks for submitting a pull request! Here are some helpful tips:

* Always create branches on and target the `develop` branch.
* Run all the tests locally and ensure that they are passing.
* Run `make format` to ensure that the code is formatted.
* Run `make check` to ensure that all checks passed successfully.
* Small commits and contributions that attempt one single goal is
preferable.
* If the idea changes or adds anything functional which will affect
users, an
AIP discussion is required first on the Aurora forum: 

https://forum.aurora.dev/discussions/AIPs%20(Aurora%20Improvement%20Proposals).
* Avoid breaking the public API (namely in engine/src/lib.rs) unless
required.
* If your PR is a WIP, ensure that you enable "draft" mode.
* Your first PRs won't use the CI automatically unless a maintainer
starts.
If this is not your first PR, please do NOT abuse the CI resources.

Checklist:
- [x] I have performed a self-review of my code
- [ ] I have documented my code, particularly in the hard-to-understand
areas
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests to prove my fix or new feature is effective and
works
- [ ] Any dependent changes have been merged
- [x] The PR is targeting the `develop` branch and not `master`
- [ ] I have pre-squashed my commits into a single commit and rebased.
-->

## Description

<!-- 
Provide a general summary of your changes. A clear overview along with
an
in-depth explanation is beneficial.

If this PR closes any issues, be sure to add "closes #<number>"
somewhere.
-->

This is a documentation only change to the `README.md` file. I updated
some portions that had some grammar issues and updated some formatting.

## Performance / NEAR gas cost considerations

N/A

## Testing

N/A, `README.md` change only.

## How should this be reviewed

README only change, so let me know if the changes make it easier to
read/follow the instructions. Happy to make more updates.

---------

Co-authored-by: Oleksandr Anyshchenko <oleksandr.anyshchenko@aurora.dev>
    @ForwardSlashBack @aleksuss
    ForwardSlashBack and aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    4fd3c37 View commit details
    Browse the repository at this point in the history

  8. ci: use github heave runners for tests (#849) 

    ## Description

Attempt to improve CI tests flow by using GitHub hosted heavy runners.
    @aleksuss
    aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    5ee8488 View commit details
    Browse the repository at this point in the history

  9. feat: add transaction for adding full access key (#847) 

    ## Description

The PR adds a transaction which allows adding the full access key into
the account of the smart contract.

## Performance / NEAR gas cost considerations

No changes.

## Testing

The corresponding test has been added.

---------

Co-authored-by: Michael Birch <michael.birch@aurora.dev>
    @aleksuss @birchmd
    aleksuss and birchmd committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    b26dfb6 View commit details
    Browse the repository at this point in the history

  10. chore: release notes 3.2.0 (#851)

    @aleksuss
    aleksuss committed Oct 17, 2023
    Configuration menu
    Copy the full SHA
    1e13373 View commit details
    Browse the repository at this point in the history