Improve CI for NAPI-RS#19983
Conversation
This is based on the information when generating a fresh napi project with `napi new`
3e83716 to
495cbf8
Compare
|
Caution Review failedPull request was closed or merged during review WalkthroughThis pull request updates GitHub Actions workflows across four files. The pnpm/action-setup action is upgraded from v4 to v6 in ci.yml, integration-tests.yml, prepare-release.yml, and release.yml. The prepare-release.yml and release.yml workflows undergo significant restructuring: the Linux build matrix removes per-target Docker container usage and instead introduces per-target build-flags, expands cargo caching configuration, adds Zig tooling setup for musl targets, implements conditional stripping logic based on target architecture, and adds targeted apt package installation for aarch64. The prepare-release.yml workflow also introduces a new 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
This PR updates the CI workflows related to NAPI-RS. So far, we've been using a custom ghcr.io based image, but these run on Node v18.
With this PR, I created a new project using
napi new, with GitHub Actions workflow setup. Then essentially ported the changes from that new project to this project (as minimal as possible).The main goal was to be able to bump NAPI-RS related dependencies and get an insiders release out. The images used in these CI jobs were blockers to get an actual (insiders) release out.
Test plan