devcon4-workshop
devcon4-workshop copied to clipboard
Bump vyper from 0.1.0b4 to 0.2.12
Bumps vyper from 0.1.0b4 to 0.2.12.
Release notes
Sourced from vyper's releases.
Vyper 0.2.12
This release fixes a memory corruption bug #2345 that was introduced in the
v0.2.x
series and was not fixed in VVE-2020-0004. Read about it further in VVE-2021-0001.Non-breaking changes and improvements:
- Optimize
calldataload
(#2352)- Add the
int256
signed integer type (#2351)- EIP2929 opcode repricing and Berlin support (#2350)
- Add
msg.data
environment variable #2343 (#2343)- Full support for Python 3.9 (#2233)
Vyper 0.2.11
This is a patch release to fix a memory corruption bug that was introduced in v0.2.9 (#2321) with excessive memory deallocation when releasing internal variables
Vyper 0.2.10
This is a quick patch release to fix incorrect generated ABIs that was introduced in v0.2.9 (#2311) where storage variable getters were incorrectly marked as
nonpayable
instead ofview
Vyper 0.2.9
No release notes provided.
Vyper 0.2.8
No release notes provided.
Vyper 0.2.7
This is a quick patch release to fix a runtime error introduced in
v0.2.6
(#2188) that could allow for memory corruption under certain conditions.Vyper 0.2.6
No release notes provided.
Vyper 0.2.5
No release notes provided.
Vyper 0.2.4
No release notes provided.
Vyper 0.2.3
Non-breaking changes and improvements:
- Show contract names in raised exceptions (#2103)
- Adjust function offsets to not include decorators (#2102)
- Raise certain exception types immediately during module-scoped type checking (#2101)
Fixes:
- Pop
for
loop values from stack prior to returning (#2110)- Type checking non-literal array index values (#2108)
- Meaningful output during
for
loop type checking (#2096)Vyper 0.2.2
... (truncated)
Changelog
Sourced from vyper's changelog.
v0.2.12
Date released: 16-04-2021
This release fixes a memory corruption bug (
[#2345](https://github.com/vyperlang/vyper/issues/2345) <https://github.com/vyperlang/vyper/pull/2345>
) that was introduced in the v0.2.x series and was not fixed inVVE-2020-0004 <https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf>
. Read about it further inVVE-2021-0001 <https://github.com/vyperlang/vyper/security/advisories/GHSA-22wc-c9wj-6q2v>
_.Non-breaking changes and improvements:
- Optimize
calldataload
([#2352](https://github.com/vyperlang/vyper/issues/2352) <https://github.com/vyperlang/vyper/pull/2352>
_)- Add the
int256
signed integer type ([#2351](https://github.com/vyperlang/vyper/issues/2351) <https://github.com/vyperlang/vyper/pull/2351>
_)- EIP2929 opcode repricing and Berlin support (
[#2350](https://github.com/vyperlang/vyper/issues/2350) <https://github.com/vyperlang/vyper/pull/2350>
_)- Add
msg.data
environment variable #2343 ([#2343](https://github.com/vyperlang/vyper/issues/2343) <https://github.com/vyperlang/vyper/pull/2343>
_)- Full support for Python 3.9 (
[#2233](https://github.com/vyperlang/vyper/issues/2233) <https://github.com/vyperlang/vyper/pull/2233>
_)v0.2.11
Date released: 27-02-2021
This is a quick patch release to fix a memory corruption bug that was introduced in v0.2.9 (
[#2321](https://github.com/vyperlang/vyper/issues/2321) <https://github.com/vyperlang/vyper/pull/2321>
_) with excessive memory deallocation when releasing internal variablesv0.2.10
THIS RELEASE HAS BEEN PULLED
Date released: 17-02-2021
This is a quick patch release to fix incorrect generated ABIs that was introduced in v0.2.9 (
[#2311](https://github.com/vyperlang/vyper/issues/2311) <https://github.com/vyperlang/vyper/pull/2311>
_) where storage variable getters were incorrectly marked asnonpayable
instead ofview
v0.2.9
THIS RELEASE HAS BEEN PULLED
Date released: 16-02-2021
Non-breaking changes and improvements:
- Add license to wheel, Anaconda support (
[#2265](https://github.com/vyperlang/vyper/issues/2265) <https://github.com/vyperlang/vyper/pull/2265>
_)- Consider events during type-check with
implements:
([#2283](https://github.com/vyperlang/vyper/issues/2283) <https://github.com/vyperlang/vyper/pull/2283>
_)- Refactor ABI generation (
[#2284](https://github.com/vyperlang/vyper/issues/2284) <https://github.com/vyperlang/vyper/pull/2284>
_)- Remove redundant checks in parser/signatures (
[#2288](https://github.com/vyperlang/vyper/issues/2288) <https://github.com/vyperlang/vyper/pull/2288>
_)- Streamling ABI-encoding logic for tuple return types (
[#2302](https://github.com/vyperlang/vyper/issues/2302) <https://github.com/vyperlang/vyper/pull/2302>
_)- Optimize function ordering within bytecode (
[#2303](https://github.com/vyperlang/vyper/issues/2303) <https://github.com/vyperlang/vyper/pull/2303>
_)- Assembly-level optimizations (
[#2304](https://github.com/vyperlang/vyper/issues/2304) <https://github.com/vyperlang/vyper/pull/2304>
_)- Optimize nonpayable assertion (
[#2307](https://github.com/vyperlang/vyper/issues/2307) <https://github.com/vyperlang/vyper/pull/2307>
_)- Optimize re-entrancy locks (
[#2308](https://github.com/vyperlang/vyper/issues/2308) <https://github.com/vyperlang/vyper/pull/2308>
_)Fixes:
... (truncated)
Commits
2c6842c
Merge pull request #2354 from vyperlang/release/0.2.123fb483c
chore: bumpversion 0.2.11 -> 0.2.1249e8d51
chore: update release notes for v0.2.123af89b5
Merge pull request #2352 from iamdefinitelyahuman/optimize-calldataloadb455c18
Merge pull request #2351 from iamdefinitelyahuman/feat-int256b0033f7
feat: optimize sequential calldataload operations9d8c3ba
refactor: move mzero merge logic into a private function8894a56
docs: add int256 to types3d6be58
chore: expand comments, cleanup2ff7329
feat: optimize int256 bounds checks- Additional commits viewable in compare view
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 commands and options
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 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) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.