Repository navigation
CI(Release): Count the Rust crates as release paths and check every pushed commit - #504
Merged
Merged
Conversation
…ushed commit The release paths were derived from the public packages only, so a fix in `crates/**` (compiled into the binding packages) or in the bundled private `internal` and `engine-js` workspaces had to use a non-release type and never released. List them in aronrepo.config.js together with the Cargo and tsdown build configuration, and regenerate the AGENTS.md block. A direct push skips the PR title check and can skip the commit hook (--no-verify, rebuilt or web-edited commits). commit-check.yml runs `aronrepo check` over every pushed range on the release branches; it reports without gating the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
aronrepo.config.jsnow lists the release paths explicitly: every package (the privateinternalandengine-jsworkspaces are bundled into published packages),crates/**withoutxtaskand test files,Cargo.toml,Cargo.lock,rust-toolchain.tomland the shared tsdown config. Before, a crate-only fix such as fa6f0f2 ([2.0] Lint sort-classes treats bound:*-classexpressions in Vue as class lists, and its "safe" fix breaks the template #493) could not use a release type and would never release.commit-check.ymlrunsaronrepo checkover every range pushed to a release branch, because direct pushes skip the PR title check and can skip the commit hook. It reports without gating the release.AGENTS.mdpolicy block regenerated;.github/RELEASING.mdmentions the new check.Since v2.0.0,
aronrepo checknow flags 14 commits (site or release-script changes with release types) instead of 15; fa6f0f2 is no longer a false positive.Verification
bun x aronrepo doctor,bun run check:releasenode --test scripts/release.test.mjs scripts/release-workspace.test.mjs scripts/release-promotion.test.mjs(44 pass)bun test scripts/validation-workflow.test.mjs scripts/editor-release-gate.test.mjs(12 pass)aronrepo check --message "Fix(Language): …" --files crates/mastercss-language/src/document.rsnow resolves to patch;crates/xtaskstill requires a non-release type.🤖 Generated with Claude Code