Skip to content

chore: release v0.42.0 - #614

Merged
goosewobbler merged 1 commit into
mainfrom
release/next
Oct 23, 2026
Merged

goosewobbler merged 1 commit into
mainfrom
release/next

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 1, 2026 •

Copy link
Copy Markdown
Contributor

Release

Merging this PR will publish v0.42.0:

  • @releasekit/version
  • @releasekit/notes
  • @releasekit/publish
  • @releasekit/release
Show all changes (54 changes, de-duplicated)

Added

  • BREAKING envelope the version and publish commands, unwrap on the pipe (cli) (PR #616)
  • uniform JSON envelope with structured errors and changed reporting (cli) (PR #608)

Fixed

  • show breaking changes in release-notes templates (notes) (PR #722)
  • flag breaking changes on the entry instead of in its description (version) (PR #720)
  • keep a commit's breaking flag when the LLM reports it as not breaking (notes) (PR #718)
  • stream LLM responses and time out only on a stall (notes) (PR #717)
  • only create missing labels during label sync (release) (PR #715)
  • record the standing PR's base after resetting to it (release) (PR #713)
  • ship complete type declarations from version, notes, publish and release (PR #712 · closes #711, #710)
  • resume a partial publish by reusing the release commit (publish) (PR #709 · closes #707)
  • BREAKING apply schema publish defaults when the config has no publish block (publish) (PR #690 · closes #667)
  • BREAKING report each error's exit-code family as its envelope category (core) (PR #708)
  • BREAKING default to conventionalcommits and reject unsupported presets (version) (PR #694 · closes #652)
  • commit a hybrid package's Cargo.toml in a direct release (release) (PR #691 · closes #678)
  • BREAKING sync every committed Cargo.lock that records a bumped crate (version) (PR #674 · closes #650)
  • push the current branch when git.branch is unset (publish) (PR #696 · closes #688)
  • keep per-package and baseline tags in --input (publish) (PR #684 · closes #675)
  • skip crates marked publish = false (publish) (PR #693 · closes #692)
  • demote Dependabot deps-dev bumps by default (notes) (PR #645 · closes #644)
  • recognise ReleaseKitError across bundled copies of core (core) (PR #651)
  • keep agent worktrees out of Biome's scope (lint) (PR #615)

Changed

  • grant statuses write in the reusable update workflow too (PR #716)
  • let the standing-PR update post its commit status (PR #714)
  • document the standing-PR body as an interface, add agent guidance (PR #619 · closes #549)
  • add the structured enhance-and-categorize eval case (notes) (PR #617)
  • add a Live Tests job, starting with notes against Ollama Cloud (PR #697 · closes #589)
  • run tests when packages/forge or packages/git change (PR #705 · closes #704)
  • cut isOllamaUnreachable's tests to the three that pin its rule (notes) (PR #702)
  • generate release notes with the OLLAMA_MODEL repo variable's model (PR #703)
  • make the LLM e2e infra-tolerant and close a false green (notes) (PR #618)
  • fix the skipped-bump entries (troubleshooting) (PR #695)
  • run the integration suite in CI and fix its stale sync-tags fixture (version) (PR #685 · closes #654)
  • flag console in package source (biome) (PR #668)
  • skip CodeQL, release preview and title checks on the standing release PR (PR #672)
  • add .git-blame-ignore-revs for the block-statement sweep (PR #680)
  • add commands and gotchas to AGENTS.md, and drop CLAUDE.md (PR #673)
  • make noExplicitAny an error outside specs and mocks (biome) (PR #682)
  • enforce block statements (biome) (PR #679 · closes #666)
  • match the README flag table to the CLI (version) (PR #677)
  • bump to 2.11.10 and opt out of agent guidance (turbo) (PR #671)
  • flag barrel files outside package entry points (biome) (PR #669)
  • enforce the shared coverage thresholds in every package's unit run (PR #670)
  • tick off shipped LLM-notes work and refresh the enablement note (roadmap) (PR #665)
  • add LLM-notes eval harness and prompt snapshot tests (notes) (PR #609)

Dependencies & version bumps

  • update package versions and lockfile (deps) (PR #681)
  • bump anthropics/claude-code-action from 1.0.240 to 1.0.252 (deps) (PR #663)
  • bump smol-toml from 1.7.1 to 1.9.0 (deps) (PR #658)
  • bump handlebars from 4.7.9 to 4.7.10 (deps) (PR #659)
  • bump dorny/paths-filter from 4.0.2 to 4.0.3 (deps) (PR #624)
  • bump anthropics/claude-code-action from 1.0.183 to 1.0.240 (deps) (PR #642)
  • bump the development-dependencies group across 1 directory with 4 updates (deps-dev) (PR #625)
  • bump the production-dependencies group across 1 directory with 6 updates (deps) (PR #613)
  • bump anthropics/claude-code-action from 1.0.179 to 1.0.183 (deps) (PR #610)
  • bump the development-dependencies group with 3 updates (deps-dev) (PR #612)

Release Notes

Edit the release notes for each package below before merging. Keep the <!-- releasekit-notes... --> marker comments — they delimit the editable region.

monorepo

Breaking:

Fixed:

Changed:

Documentation:

Developer:

Full Changelog: 0.41.2...0.42.0


Merge this PR to publish. The release will be triggered automatically.

Updated automatically by ReleaseKit

@github-actions

github-actions Bot commented Aug 1, 2026 •

Copy link
Copy Markdown
Contributor Author
Release manifest (do not edit)

@github-actions github-actions Bot changed the title chore: release v0.41.3 chore: release v0.42.0 Aug 1, 2026
@github-actions
github-actions Bot force-pushed the release/next branch 2 times, most recently from 9fa013e to 557f6f5 Compare August 1, 2026 18:29
@github-actions
github-actions Bot force-pushed the release/next branch 3 times, most recently from d7dafe7 to 77bfe70 Compare October 23, 2026 15:41
@goosewobbler goosewobbler added the release:preview-notes ReleaseKit: generate editable release notes in the standing PR body label Oct 23, 2026
@github-actions
github-actions Bot force-pushed the release/next branch 2 times, most recently from e237e18 to 4cb0bdc Compare October 23, 2026 17:00
@goosewobbler
goosewobbler merged commit 5b1929a into main Oct 23, 2026
1 check passed
@goosewobbler
goosewobbler deleted the release/next branch October 23, 2026 17:57
@goosewobbler goosewobbler removed the release:preview-notes ReleaseKit: generate editable release notes in the standing PR body label Oct 23, 2026
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>
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment