Repository navigation
chore: release v0.42.0 - #614
Merged
Merged
Conversation
Contributor
Author
Release manifest (do not edit) |
github-actions
Bot
force-pushed
the
release/next
branch
from
August 1, 2026 18:14
938c929 to
ce5cbe9
Compare
github-actions
Bot
force-pushed
the
release/next
branch
from
August 1, 2026 18:19
ce5cbe9 to
1f093ba
Compare
github-actions
Bot
force-pushed
the
release/next
branch
2 times, most recently
from
August 1, 2026 18:29
9fa013e to
557f6f5
Compare
github-actions
Bot
force-pushed
the
release/next
branch
from
August 1, 2026 18:37
557f6f5 to
49e0541
Compare
This was referenced Aug 1, 2026
This was referenced Aug 10, 2026
Merged
This was referenced Sep 7, 2026
This was referenced Sep 21, 2026
This was referenced Sep 28, 2026
9 of 20 tasks
github-actions
Bot
force-pushed
the
release/next
branch
3 times, most recently
from
October 23, 2026 15:41
d7dafe7 to
77bfe70
Compare
github-actions
Bot
force-pushed
the
release/next
branch
from
October 23, 2026 15:54
77bfe70 to
58cd571
Compare
This was referenced Oct 23, 2026
3 of 20 tasks
github-actions
Bot
force-pushed
the
release/next
branch
from
October 23, 2026 16:15
58cd571 to
6367541
Compare
7 of 20 tasks
github-actions
Bot
force-pushed
the
release/next
branch
2 times, most recently
from
October 23, 2026 17:00
e237e18 to
4cb0bdc
Compare
This was referenced Oct 23, 2026
github-actions
Bot
force-pushed
the
release/next
branch
from
October 23, 2026 17:17
4cb0bdc to
816cb21
Compare
7 of 20 tasks
github-actions
Bot
force-pushed
the
release/next
branch
from
October 23, 2026 17:39
816cb21 to
3835af3
Compare
6 of 20 tasks
github-actions
Bot
force-pushed
the
release/next
branch
from
October 23, 2026 17:53
3835af3 to
4bda724
Compare
6 of 20 tasks
goosewobbler
pushed a commit
that referenced
this pull request
Oct 23, 2026
GitHub's default squash title for a single-commit PR is the commit's subject, so v0.42.0 landed on main as "chore: release preparation (#614)" instead of "chore: release v0.42.0 (#614)". The release branch's commit now uses the PR title, falling back to the fixed subject when a custom title matches no skip pattern. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6 of 20 tasks
goosewobbler
added a commit
that referenced
this pull request
Oct 24, 2026
…le (#729) * fix(release): commit the standing PR's release branch with the PR title GitHub's default squash title for a single-commit PR is the commit's subject, so v0.42.0 landed on main as "chore: release preparation (#614)" instead of "chore: release v0.42.0 (#614)". The release branch's commit now uses the PR title, falling back to the fixed subject when a custom title matches no skip pattern. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(release): keep CI-skip markers out of the release commit A custom standing-PR title carrying a CI-skip marker would otherwise reach the release commit, and a single-commit squash would copy it onto main and skip the publish workflow. Such a title now falls back to the fixed subject. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(release): align standing PR title with safe commit subject Co-authored-by: Cursor <cursoragent@cursor.com> * fix(release): warn when the standing PR title falls back A custom title that matches no skip pattern, or carries a CI-skip marker, was silently replaced on both the commit and the PR. The run now warns, and the `title` option's description says when the fallback applies. The commit subject and PR title are one variable again, and one test covers both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(release): drop a comment the title check now covers The comment below says the title must match a skip pattern, and the code enforces it, so the note on the default titles repeated it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(release): tighten the standing PR title comment Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(release): fall back to the fixed standing PR title only when it's safe The fallback subject was never checked against release.ci.skipPatterns. With custom or empty patterns, even the default title failed the check and was replaced by a subject that matched nothing either, so the PR lost its title and the merge still triggered another standing-PR update. A title with a CI-skip marker is still always replaced. A title the skip patterns miss is replaced only when they match the fallback; otherwise it's kept, with a warning that the merge will trigger another update. Tests cover custom and empty skip patterns, the warnings, and retitling an existing standing PR. The ci-setup and release README tables now state the rule and list ${tag}. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(release): honour git.skipHooks on the standing PR's release commit The release-branch commit now carries the standing PR title, which a consumer configures, so a commit-msg hook such as commitlint can reject it. The publish stage's commit already respects git.skipHooks; the standing PR's commit now does too. Unset still runs the hooks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(release): state the standing PR title fallback the same way everywhere ci-setup.md said the fallback applied only when the skip patterns match it, but a title with a CI-skip marker is always replaced. The schema description now says which titles are replaced, and both tables name the non-sync default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(release): drop the half of the title comment the warnings repeat Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.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.
Release
Merging this PR will publish v0.42.0:
@releasekit/version@releasekit/notes@releasekit/publish@releasekit/releaseShow all changes (54 changes, de-duplicated)
Release Notes
monorepoBreaking:
versionandpublishcommands now emit standard JSON envelopes and support--output <path>, with downstream stages able to unwrap those envelopes for chaining. (feat(cli)!: envelope the version and publish commands, unwrap on the pipe #616) (feat(cli)!: envelope the version and publish commands, unwrap on the pipe #616)release,gate, andstanding-prresults, including structured errors andchanged-state reporting. (feat(cli): uniform JSON envelope with structured errors and changed reporting #608)publishblock now publish detected Rust and Dart packages by default while still honoring top-level Git settings. (fix(publish)!: apply schema publish defaults when the config has no publish block #690) (fix(publish)!: apply schema publish defaults when the config has no publish block #690, crates.io and pub.dev publishing stays off when the config has no publish block #667)conventionalcommitsand rejects unsupported preset names, including the formerconventionalandconventional-commitsaliases. (fix(version)!: default to conventionalcommits and reject unsupported presets #694) (fix(version)!: default to conventionalcommits and reject unsupported presets #694, Default version.preset ("conventional") can't be loaded; a bad preset crashes release/standing-pr with an unhandled rejection and no envelope #652)Cargo.lockaffected by a bumped crate without requiring Cargo, and fails on ambiguous or unsupported locks. (fix(version)!: sync every committed Cargo.lock that records a bumped crate #674) (fix(version)!: sync every committed Cargo.lock that records a bumped crate #674, Cargo.lock files go stale at every release, so each one needs a manual sync PR #650)ReleaseKitErrorinstances across bundled core copies so JSON commands reported specific error codes and metadata and returned the corresponding exit codes. (fix(core): recognise ReleaseKitError across bundled copies of core #651)Fixed:
**BREAKING**marker. (fix(notes): show breaking changes in release-notes templates #722) (fix(notes): show breaking changes in release-notes templates #722)version,notes,publish, andreleasepackages now ship complete type declarations, and the resulting type checks exposed and fixed backfill and publish-ledger bugs. (fix: ship complete type declarations from version, notes, publish and release #712) (fix: ship complete type declarations from version, notes, publish and release #712, version, notes and publish ship type declarations that resolve to any #711, backfill --config ignores the path when loading the publish config #710)Cargo.tomlfiles alongside their package manifests. (fix(release): commit a hybrid package's Cargo.toml in a direct release #691) (fix(release): commit a hybrid package's Cargo.toml in a direct release #691, Direct release doesn't commit a hybrid package's Cargo.toml bump #678)git.branchis unset, while detached HEAD runs still require an explicit branch. (fix(publish): push the current branch when git.branch is unset #696) (fix(publish): push the current branch when git.branch is unset #696, Publish pushes main instead of the current branch whenever a git block is configured #688)publish --inputnow preserves per-package and baseline tags, enabling per-package mode and ensuring only tags created by the run are pushed. (fix(publish): keep per-package and baseline tags in --input #684) (fix(publish): keep per-package and baseline tags in --input #684, publish --input drops per-package tags and baseline tags from the version output #675)publish = falseorpublish = []instead of sending them to crates.io. (fix(publish): skip crates marked publish = false #693) (fix(publish): skip crates marked publish = false #693, Cargo publish ignores publish = false in Cargo.toml #692)deps-devscope are now demoted to the dependencies section by default. (fix(notes): demote Dependabot deps-dev bumps by default #645) (fix(notes): demote Dependabot deps-dev bumps by default #645, Changelog: Dependabotdeps-devbumps aren't demoted into "Dependencies & version bumps" #644).claude/worktreesfrom Biome so agent checkouts no longer broke repository-wide linting. (fix(lint): keep agent worktrees out of Biome's scope #615)Changed:
minimax-m3.1-flash:cloud, matching theOLLAMA_MODELvariable used by live tests. (chore: generate release notes with the OLLAMA_MODEL repo variable's model #703) (chore: generate release notes with the OLLAMA_MODEL repo variable's model #703)smol-tomlfrom 1.7.1 to 1.9.0. (chore(deps): bump smol-toml from 1.7.1 to 1.9.0 #658)dorny/paths-filterGitHub Action to v4.0.3, including its multiline-filename security fix. (chore(deps): bump dorny/paths-filter from 4.0.2 to 4.0.3 #624)@typescript-eslint/parser,@vitest/eslint-plugin, ESLint, and Turborepo in the development dependency group. (chore(deps-dev): bump the development-dependencies group across 1 directory with 4 updates #625)smol-tomlin the production dependency group. (chore(deps): bump the production-dependencies group across 1 directory with 6 updates #613)@vitest/eslint-plugin, ESLint, and Turborepo in the development dependency group. (chore(deps-dev): bump the development-dependencies group with 3 updates #612)Documentation:
@releasekit/versionREADME flag table with the CLI's actual options, aliases, and bump types. (docs(version): match the README flag table to the CLI #677)Developer:
statuses: write, allowing its commit status to be posted successfully. (ci: grant statuses write in the reusable update workflow too #716) (ci: grant statuses write in the reusable update workflow too #716)statuses: write, allowing commit statuses to reach the release branch. (ci: let the standing-PR update post its commit status #714) (ci: let the standing-PR update post its commit status #714)forgeorgitpackages. (ci: run tests when packages/forge or packages/git change #705) (ci: run tests when packages/forge or packages/git change #705, CI skips every test for PRs that only change packages/forge or packages/git #704)noConsolerule for package source while exempting logger and CLI output paths. (chore(biome): flag console in package source #668) (chore(biome): flag console in package source #668)noExplicitAnyrule to an error for production TypeScript while retaining exceptions for specs and mocks. (chore(biome): make noExplicitAny an error outside specs and mocks #682)AGENTS.mdedits. (chore(turbo): bump to 2.11.10 and opt out of agent guidance #671)noBarrelFilerule outside package entry points and removed flagged internal barrels without changing public APIs. (chore(biome): flag barrel files outside package entry points #669)Full Changelog: 0.41.2...0.42.0
Updated automatically by ReleaseKit