ci: automate releases with Release Please - #432
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releasing NitroSQLite currently requires a manually prepared version PR before the publication workflow can run. This PR replaces release-it with Release Please and makes one workflow dispatch prepare, merge, tag, publish and announce the release. It follows the release setup in expo-native-variants, with the extra steps needed for NitroSQLite's two packages and native example.
The workflow accepts patch, minor, major or an exact stable version on any branch containing the automation. Release Please updates all package versions and internal dependencies together, and the workflow regenerates the workspace and CocoaPods lockfiles. It waits for all reported CI checks and merges through GitHub's normal checks and review rules.
Both packages are validated before either is published through npm trusted publishing with provenance. Version 9 keeps its legacy channel; other maintenance releases cannot move latest backwards. A retry can resume an existing tag and skip a package only if its published version records the same release commit.
The GitHub release stays a draft until the Android APK is attached. An announcement supplied in the workflow form or a versioned Markdown file is followed by a divider, the complete grouped changelog and a new contributors section when GitHub detects first-time contributors.
Release tests cover maintenance baselines, version synchronization through Release Please's actual updater, announcement assembly, publication preflight failures and partial publication retries. The publishing tests use simulated commands and registry responses. Credential setup and recovery steps are documented in the release guide.