chore: release main#175
Open
r6e-release-please[bot] wants to merge 1 commit into
Open
Conversation
r6e-release-please
Bot
force-pushed
the
release-please--branches--main
branch
16 times, most recently
from
8d0f9aa to
a603b9c
Compare
3 tasks
r6e
added a commit
that referenced
this pull request
May 17, 2026
The release-please PR (#175) was failing the Spell check job because the CHANGELOG.md entries it generates contain short SHA-1 commit prefixes that collide with English-word heuristics in crate-ci/typos's default dictionary: error: `ba` should be `by`, `be` ╭▸ ./crates/paksmith-core/CHANGELOG.md:13:133 │ 13 │ … Task 10) ([#178](.../issues/178)) ([ba40798](.../commit/ba40798… ╰╴ `ba40798` is a valid git short-hash, not a typo. The failure recurs on every release-please regeneration because the CHANGELOG grows monotonically — any hex prefix starting with a sequence typos recognizes as a near-English word would re-trigger. Fix: add `CHANGELOG.md` and `**/CHANGELOG.md` to typos' `[files] extend-exclude`. Auto-generated content shouldn't be spell-checked — the underlying commit messages are already validated at PR-title time, and CHANGELOGs are derived mechanically from those. Per-file regex exclusions (`extend-ignore-re` for hash-shaped strings) would be more surgical but also more fragile (release- please could change link format). Excluding the whole file is cleaner and unblocks the release pipeline immediately. The companion Title-validator failure on #175 is unrelated and should resolve when release-please regenerates the PR after this fix lands on main — the current PR title (`chore: release main`) already passes the validator's lowercase-first-letter rule; earlier auto-generated titles likely didn't. Verified locally: `typos .` from repo root exits clean with the new config. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
r6e-release-please
Bot
force-pushed
the
release-please--branches--main
branch
11 times, most recently
from
1e21908 to
f3f5ec2
Compare
r6e-release-please
Bot
force-pushed
the
release-please--branches--main
branch
24 times, most recently
from
60abd00 to
70c234f
Compare
r6e-release-please
Bot
force-pushed
the
release-please--branches--main
branch
from
70c234f to
a144a9c
Compare
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.
🤖 I have created a release beep boop
paksmith-bench: 0.0.1
Dependencies
0.1.1
0.1.1 (2026-05-20)
Features
Bug Fixes
Dependencies
0.1.1
0.1.1 (2026-05-20)
Features
Bug Fixes
paksmith-core-tests: 0.0.1
Dependencies
paksmith-fixture-gen: 0.0.1
Dependencies
This PR was generated with Release Please. See documentation.