Repository navigation
ci: open a release PR twice a month when the published package changed - #66
Merged
Merged
Conversation
Adds scripts/release-check.sh and a scheduled release-check workflow that runs release-pr.sh only when shipped files, bundled zstd or package entry points/peer deps changed since the last tag. Renovate now tracks the zstd submodule by release tag (manual review).
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
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.
Description
A scheduled workflow (1st and 15th, or manual) runs
scripts/release-check.shand opens a patch release PR viarelease-pr.shonly when something that ships to npm changed since the last tag:src,cpp,android,nitrogen, the podspec, bundled zstd, orpackage.jsonentry points/files/peer deps. Dev-tooling-only changes (all of1.4.1–1.4.9) no longer warrant a release.Renovate now tracks the zstd submodule by release tag (
.gitmodulestag→branch, which Renovate reads), with automerge off so a zstd bump gets a review before the next release check picks it up.Release PRs opened by the bot use
GITHUB_TOKEN, so CI doesn't run on them; merging still triggersrelease.yml.