Skip to content

Repository navigation

ci(release): automate drafts with the audited official CLI #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CruxExperts merged 2 commits into from
Oct 23, 2026
Merged

ci(release): automate drafts with the audited official CLI #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6aceadb
ci(release): prepare guarded Release Please drafts
CruxExperts Oct 23, 2026
d9e4f7a
ci(release): run the audited official Release Please CLI
CruxExperts Oct 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ The production CLI and dashboard share an operations service. Do not add an alte

## Commits and pull requests

Use conventional commit subjects such as `fix: reject unsafe restore targets` or `docs: clarify replica setup`. Normal batches use a patch increment unless the commit body includes a deliberate `Release-Type: major|minor|patch|none` trailer. See [release versioning](../docs/VERSIONING.md).
Use conventional commit subjects such as `fix: reject unsafe restore targets` or `docs: clarify replica setup`. Release Please prepares draft release PRs with a patch increment, including for `feat:` commits. Use a supported `Release-As: X.Y.Z` body trailer for an exact different version; historical `Release-Type` trailers are review notes and are not parsed by the bot. Prepare and sign the release branch before marking it ready. See [release versioning](../docs/VERSIONING.md#prepare-the-release-pull-request).

Open pull requests against `main`, complete the [pull-request template](pull_request_template.md), and describe the exact checks and platforms exercised. Do not describe fixture or Garage testing as B2/AWS or Ubuntu package qualification. A successful file restore verifies file data; it does not demonstrate application recovery.

Expand Down
Loading
Loading