Skip to content

Version Packages - #471

Merged
kraenhansen merged 1 commit into
mainfrom
changeset-release/main
Oct 12, 2026
Merged

kraenhansen merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

gyp-to-cmake@0.7.0

Minor Changes

  • fd0bfde: Translate target-level cflags from binding.gyp into private CMake compile
    options. The parser now validates that cflags is an array of strings, and the
    generated options preserve command expansion and escaped spaces.

react-native-node-api@1.2.0

Minor Changes

  • 44617d2: Add a --fail-on-error option to react-native-node-api link. By default,
    unresolvable dependencies continue to be skipped with a warning; the new flag
    instead surfaces the original package-resolution error and exits unsuccessfully,
    which makes broken package exports configurations diagnosable in CI.

Patch Changes

  • 14e5119: Parse binary Info.plist files in-process with bplist-parser instead of
    converting them with plutil, so reading a framework's plist no longer
    rewrites the file or requires macOS.
  • 8d125fa: Preserve Node.js module resolution precedence when a JavaScript file and native addon share a basename: require('./foo') no longer gets rewritten to load a Node-API addon when a same-named foo.js/.cjs/.mjs/.json file exists alongside it, since that source file is what require() actually resolves to. An explicit require('./foo.node') is unaffected.
  • ba6a527: Log the original package resolution error during dependency scanning so invalid package entry points include the missing path.
  • c8d5b80: Declare the Node.js versions that support loading ESM from CommonJS so package
    managers warn before the CLI loads its ESM dependencies on an incompatible
    runtime.
  • weak-node-api@0.1.1

cmake-rn@0.8.1

Patch Changes

  • 4376787: Apply --code-signing-allowed to CMake framework targets too. It was only
    passed when building plain dynamic libraries, so framework targets built
    through xcodebuild archive/install were always signed, leaving a
    _CodeSignature directory in each framework.
  • Updated dependencies [14e5119]
  • Updated dependencies [8d125fa]
  • Updated dependencies [ba6a527]
  • Updated dependencies [c8d5b80]
  • Updated dependencies [44617d2]
    • react-native-node-api@1.2.0
    • weak-node-api@0.1.1

ferric-cli@0.4.4

Patch Changes

  • Updated dependencies [14e5119]
  • Updated dependencies [8d125fa]
  • Updated dependencies [ba6a527]
  • Updated dependencies [c8d5b80]
  • Updated dependencies [44617d2]
    • react-native-node-api@1.2.0
    • weak-node-api@0.1.1

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from 24ddee4 to 9e6a775 Compare October 11, 2026 22:04
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9e6a775 to cce3b03 Compare October 12, 2026 06:45
@kraenhansen kraenhansen self-assigned this Oct 12, 2026
@kraenhansen
kraenhansen merged commit 726829a into main Oct 12, 2026
9 checks passed
@kraenhansen
kraenhansen deleted the changeset-release/main branch October 12, 2026 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant