ta-math icon indicating copy to clipboard operation
ta-math copied to clipboard

Update dependency assemblyscript to v0.28.9

Open renovate[bot] opened this issue 3 years ago โ€ข 3 comments

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
assemblyscript (source) 0.21.6 -> 0.28.9 age adoption passing confidence

Release Notes

AssemblyScript/assemblyscript (assemblyscript)

v0.28.9

Compare Source

New features
Other

v0.28.8

Compare Source

New features

v0.28.7

Compare Source

Bug fixes

v0.28.6

Compare Source

New features

v0.28.5

Compare Source

Bug fixes

v0.28.4

Compare Source

Bug fixes
Other
  • chore: refactor ensureConstructor with CommonNames instead of raw string (#โ€‹2935) (69cc1cb)

v0.28.3

Compare Source

Bug fixes

v0.28.2

Compare Source

New features
Bug fixes
Other

v0.28.1

Compare Source

Bug fixes

v0.28.0

Compare Source

Breaking changes
Bug fixes

v0.27.37

Compare Source

Bug fixes
  • Math.pow constant optimization behaves inconsistently in different versions of node (#โ€‹2920) (ae8c46c) use the pow function compiled by AS bootstrap to optimize the constant propagation of pow

v0.27.36

Compare Source

Bug fixes

v0.27.35

Compare Source

New features
Other

v0.27.34

Compare Source

Bug fixes

v0.27.33

Compare Source

New features
Other

v0.27.32

Compare Source

New features
Other
  • chore: enhance comment for extract_lane functions to include "idx" argument needs to be compile time constant (#โ€‹2890) (40850fe)

v0.27.31

Compare Source

New features
Other

v0.27.30

Compare Source

Bug fixes
  • strictly check operator overload ambiguity (#โ€‹2762) (dfc8a65) Operator overload is an internal mechanism, it can support to compare user-defined class, but it need to be limited. a == b and b == a should run the same function and get the same result in semantic level. Allowing ambiguity is bug prone.
  • report error for mulitple union type (#โ€‹2872) (1847c8f)
Other

v0.27.29

Compare Source

Bug fixes
Other

v0.27.28

Compare Source

Bug fixes
Other

v0.27.27

Compare Source

Bug fixes
Other

v0.27.26

Compare Source

Bug fixes
Other
  • Compile incrementors in for loops within the initializer's flow (#โ€‹2826) (9102c05) It turns out that incrementors were compiled with the body's flow, which meant that the incrementor had access to local variables declared in the body. Now, incrementors no longer have access to such variables.

    Fixes #โ€‹2825.

  • Binaryen on transform (#โ€‹2832) (9605c03)

    • Expose binaryen instance on transform

    • Fix invalid import in generated output

v0.27.25

Compare Source

Bug fixes

v0.27.24

Compare Source

Bug fixes

v0.27.23

Compare Source

Bug fixes
Other

v0.27.22

Compare Source

New features

v0.27.21

Compare Source

Bug fixes

v0.27.20

Compare Source

Bug fixes

v0.27.19

Compare Source

Bug fixes

v0.27.18

Compare Source

Bug fixes
Other

v0.27.17

Compare Source

Bug fixes
  • placeholder commit for aspublish (#โ€‹2789) (f055bff) The commit that fixed the regression didn't start with "fix:" and such, so this commit accounts for that instead.
Other

v0.27.16

Compare Source

Bug fixes
Other

v0.27.15

Compare Source

Bug fixes

v0.27.14

Compare Source

Bug fixes
Other

v0.27.13

Compare Source

Bug fixes

v0.27.12

Compare Source

Bug fixes

v0.27.11

Compare Source

Bug fixes
Other

v0.27.10

Compare Source

Bug fixes

v0.27.9

Compare Source

Bug fixes

v0.27.8

Compare Source

Bug fixes

v0.27.7

Compare Source

Bug fixes
Other

v0.27.6

Compare Source

Bug fixes

v0.27.5

Compare Source

Bug fixes

v0.27.4

Compare Source

Bug fixes

v0.27.3

Compare Source

Bug fixes
Other

v0.27.2

Compare Source

New features
Bug fixes
  • Update Binaryen to 112.0.0-nightly.20230411 (#โ€‹2683) (f7571a4) Emscripten lowered the default stack size of emitted modules to 64kb recently, easily producing stack overflows in the optimizer. This version of Binaryen increases stack size to the previous 5mb again.
Other

v0.27.1

Compare Source

Bug fixes
Other

v0.27.0

Compare Source

Breaking changes
  • Check global uses more strictly (#โ€‹2632) (5cbbf84) Use of global variables (in the Wasm sense) is now checked more strictly to prevent undesirable execution order. If the compiler detects that it is possible that a variable might not have been initialized when accessed, a diagnostic is produced. It cannot be ruled out that some amount of existing code will be affected, since such checks are performed at runtime in JS but are proven at compile time in AS. If encountered, the fix is to move the variable's declaration up, say before the first invocation of a function (that might call another function) accessing the variable, so it is guaranteed that it is initialized before its first use.
Bug fixes
Other

v0.26.7

Compare Source

Bug fixes

v0.26.6

Compare Source

Bug fixes
Other

v0.26.5

Compare Source

Bug fixes
Other

v0.26.4

Compare Source

Bug fixes

v0.26.3

Compare Source

New features

v0.26.2

Compare Source

Bug fixes
Other

v0.26.1

Compare Source

Bug fixes
  • Mitigate endless loop in (invalid) override discovery (d46bfeb)
  • Check ASI upon unusual trailing expressions (#โ€‹2252) (282d924)
Other

v0.26.0

Compare Source

Breaking changes
  • Add LUB computation for class types (#โ€‹2594) (4b3b390) Binary and ternary expressions now compute and evaluate to the least upper bound of two not identical class type inputs in the absence of a better fitting contextual type. Technically a breaking change, yet likely without noticeable effects on existing code.
Bug fixes
  • Defuse assert in lookupPropertyAccessExpression after prior error (82812de)
  • Support trailing comma in function type parameters (#โ€‹2608) (1ff71e5)
Other

v0.25.2

Compare Source

New features
Bug fixes
Other

v0.25.1

Compare Source

Bug fixes
Other

v0.25.0

Compare Source

Breaking changes
  • Fix variable initialization checks / revise flow logic (#โ€‹2578) (6717de0) Initialization of global variables sometimes wasn't guaranteed before, allowing unsafe behavior if initialization indeed wasn't performed before access. To mitigate, variables from now on require either an initializer, a primitive type with a trivial default value (typically 0), a nullable type (if a reference, defaulting to null) or otherwise annotation with definitive assignment (i.e. let someObject!: ..., then inserting a runtime check upon access).
Other

v0.24.1

Compare Source

Bug fixes

v0.24.0

Compare Source

Breaking changes
  • Implicitly inherit from Object (#โ€‹2559) (688dcd2) Constant class ids of String, ArrayBuffer etc. moved one value up, with Object now represented by ID=0.

v0.23.1

Compare Source

Bug fixes

v0.23.0

Compare Source

Breaking changes
  • Remove no longer used half of RTTI (#โ€‹2555) (a565d73) RTTI at __rtti_base no longer contains base class ids and now is just type flags.
  • Make class fields a special kind of property (#โ€‹2548) (0fd4db2) Element kinds FIELD and FIELD_PROTOTYPE and elements Field and FieldPrototype have been removed. Instead, Property inherit previous Field functionality, indicated by property.isField.
Other

v0.22.0

Compare Source

Breaking changes
  • Refactor enum identifiers to TitleCase and apply some changes in AST nodes (#โ€‹2501) ([a7d10ba](https://redirect.github.com/AssemblyScript/assemblyscript/commit/a7d10ba0c50caf0be8b29dcb4c71d378b0d05dc6

Configuration

๐Ÿ“… Schedule: Branch creation - "on sunday" (UTC), Automerge - At any time (no schedule defined).

๐Ÿšฆ Automerge: Enabled.

โ™ป Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

๐Ÿ”• Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate[bot] avatar Oct 30 '22 02:10 renovate[bot]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

renovate[bot] avatar Oct 30 '22 02:10 renovate[bot]

โš  Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

โ™ป Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"3.2.3" from the root project
npm ERR!   peer rollup@">=1.26.3" from [email protected]
npm ERR!   node_modules/rollup-plugin-typescript2
npm ERR!     dev rollup-plugin-typescript2@"0.34.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rollup@">=0.60.0 <3" from [email protected]
npm ERR! node_modules/rollup-plugin-babel
npm ERR!   dev rollup-plugin-babel@"4.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/rollup
npm ERR!   peer rollup@">=0.60.0 <3" from [email protected]
npm ERR!   node_modules/rollup-plugin-babel
npm ERR!     dev rollup-plugin-babel@"4.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-11T04_36_02_507Z-debug-0.log

renovate[bot] avatar Oct 30 '22 02:10 renovate[bot]

โš ๏ธ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

โ™ป Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"3.2.3" from the root project
npm ERR!   peer rollup@">=1.26.3" from [email protected]
npm ERR!   node_modules/rollup-plugin-typescript2
npm ERR!     dev rollup-plugin-typescript2@"0.34.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer rollup@">=0.60.0 <3" from [email protected]
npm ERR! node_modules/rollup-plugin-babel
npm ERR!   dev rollup-plugin-babel@"4.4.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/rollup
npm ERR!   peer rollup@">=0.60.0 <3" from [email protected]
npm ERR!   node_modules/rollup-plugin-babel
npm ERR!     dev rollup-plugin-babel@"4.4.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-12-03T18_35_23_878Z-debug-0.log

renovate[bot] avatar Jun 22 '24 02:06 renovate[bot]