Skip to content

ci: open a release PR twice a month when the published package changed - #66

Merged
Andarius merged 1 commit into
mainfrom
ci/scheduled-release-check
Nov 14, 2026
Merged

Andarius merged 1 commit into
mainfrom
ci/scheduled-release-check

Conversation

@Andarius

Copy link
Copy Markdown
Owner

Description

A scheduled workflow (1st and 15th, or manual) runs scripts/release-check.sh and opens a patch release PR via release-pr.sh only when something that ships to npm changed since the last tag: src, cpp, android, nitrogen, the podspec, bundled zstd, or package.json entry points/files/peer deps. Dev-tooling-only changes (all of 1.4.1–1.4.9) no longer warrant a release.

Renovate now tracks the zstd submodule by release tag (.gitmodules tag → 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 triggers release.yml.

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).
@Andarius
Andarius merged commit ba10b75 into main Nov 14, 2026
8 checks passed
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