Skip to content

Conversation

@balena-renovate
Copy link
Contributor

@balena-renovate balena-renovate bot commented Mar 19, 2025

This PR contains the following updates:

Package Type Update Change
neon (source) dependencies major 0.10 -> 1.0

Release Notes

neon-bindings/neon (neon)

v1.1.1

Compare Source

Hotfix for Node-API versions lower than 5 (#​1106).

v1.1.0

Compare Source

Continued Commitment to Compatibility

Our strong commitment to compatibility since the 1.0 release remains unchanged. New functionality
that has not yet stabilized is published under feature flags, so the only breaking changes that we
expect to publish are those that affect the unstable features, or, as always, safety bugfixes.

Version 1.1.1

Hotfix for Node-API versions lower than 5 (#​1106).

Version 1.1.0

New Features
Bugfixes
  • Fix panic when borrowing empty buffer or typed array (#​1058)
  • Fix build script behavior based on cargo diagnostics format change (#​1039)

Version 1.1.0-alpha.2

Breaking Changes (unstable features only)
  • Convert snake_case to camelCase when exporting functions (#​1084)
  • Remove FromArgs impl on T: TryFromJs and add cx.{arg, arg_opt} (#​1096)
Other
  • Relax lifetime constraints on With (#​1086)
  • Add JsBox::{deref, as_inner} to get long-lived reference to JsBox contents (#​1087)
  • Add extractors for TypedArrays (#​1089)
  • Add extractors for common container types (#​1091)

Version 1.1.0-alpha.1

Breaking Changes (unstable features only)
  • TryIntoJs and TryFromJs take Cx instead of generic Context (#​1062)
Bugfixes
  • Fix panic when borrowing empty buffer or typed array (#​1058)
Other
  • More reliable checking for Result types in #[export] (#​1057)
  • Allow users to take Cx instead of generic Context (#​1048)
  • Introduce With for TryIntoJs (#​1059)
  • Add tokio async runtime support to #[export] (#​1055)
  • Add TryIntoJs and TryFromJs for common container types (#​1066)
  • Allow Cx in exported functions (#​1068)

Version 1.1.0-alpha.0

Bugfixes
  • Fix build script behavior based on cargo diagnostics format change (#​1039)
Other

v1.0.0

Compare Source

Commitment to Compatibility

The release of Neon 1.0 marks our commitment to backwards-compatibility: starting with 1.0.0, Neon users can be confident that future upgrades to Neon 1.x versions should never require code changes (with the possible exception of safety bugfixes, which we expect to be rare). We also do not anticipate releasing new major versions often and do not have any plans to do so for now.

Breaking Changes

  • Remove the generic parameter from JsFunction (#​989)
  • JsArray::new takes a usize instead of a u32 (#​988)
  • Made Context::global read a key and added Context::global_object (#​987)
  • Deprecated feature flags were removed

Bug fixes

  • Fix unhandledRejection with JsPromise::to_future (#​1008)
  • Typo in cargo-cp-artifact help (#​998)
  • Typo in README (#​1012)

Other

#​1010

  • Relaxed error behavior on missing Node-API symbols. Neon will panic on first use instead of aborting the process at module load time.
  • Bumped dependency versions
  • Changed to edition 2021
  • Updated support matrix to Node 18, 20, and 21

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 has been generated by Renovate Bot.

@balena-renovate
Copy link
Contributor Author

balena-renovate bot commented Mar 19, 2025

⚠️ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `neon`.
    ... required by package `balena-systemd v0.5.10 (/tmp/renovate/repos/github/balena-io-modules/node-systemd)`
versions that meet the requirements `^1.0` are: 1.0.0

the package `balena-systemd` depends on `neon`, with features: `channel-api` but `neon` does not have these features.


failed to select a version for `neon` which could resolve this conflict

@balena-renovate balena-renovate bot force-pushed the renovate/neon-1.x branch 2 times, most recently from aa96da7 to a9cfc4b Compare April 7, 2025 23:50
Update neon from 0.10.1 to 1.0.0

Change-type: patch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant