chore(release): 6.66.3 - #224
Merged
Merged
Conversation
Ships the user-facing fixes accumulated since 6.66.2, none of which
reach anyone until this is published:
- five lint false positives that were driving users to disable
`bashrs lint` (#219, GH-217, GH-209)
- CLI stack overflow from an oversized clap frame (#216, #215)
- RUSTSEC-2026-0204, crossbeam-epoch 0.9.20 (#210)
plus internal repairs: kani harnesses compile under cfg(kani) again
(#221), bashrs-oracle's test module compiles and the workspace is
actually tested (#223), and a workflow template stopped being run as a
workflow (#222).
Cargo.lock regenerated in the same commit -- forjar's 1.12.4 release
tripped its lockfile-preflight by bumping Cargo.toml alone.
Co-Authored-By: Claude Opus 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
1 participant
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.
Ships the user-facing fixes accumulated since 6.66.2. None of them reach anyone until this is published — crates.io is still on 6.66.2.
Fixed
bashrs lint(#219, Lint rules parse quoted-heredoc bodies as shell: SC1007 false-positives on embedded Python #217, bashrs lint Makefile — false positives + --fail-on error flag not honored in v6.66.1 prebuilt #209). Diagnostics inside quoted heredocs (<<'EOF') are no longer emitted at all — a quoted heredoc body is literal text, not shell, so SC1007 and friends had no business firing there. MAKE003 now skips Make's$$escape before checking quoting; MAKE010 recognises|| exit/|| return/|| dietails as error handling; MAKE016 is retired outright, because its autofix corrupted Makefiles.cargo test(2 MB thread stacks) hit it;cargo nextest(8 MB process stacks) hid it.Internal
cfg(kani)again andmake verify-kanino longer swallows failures with|| true(#221). The crate hadn't built undercfg(kani)since the harnesses were added. Two harnesses that could not fail were deleted rather than repaired. They still don't converge — #220.bashrs-oracle's extracted test module compiles again, and CI runs--workspace --libso a rotting member is loud (#223)..github/workflows/was being executed as a real workflow (#222).Release hygiene
Cargo.lockis regenerated in this same commit (all 5 workspace members → 6.66.3, zero6.66.2left). forjar's 1.12.4 release tripped its ownlockfile-preflightby bumpingCargo.tomlalone; not repeating that.Publish is gated on the mandatory infra clean-room run, and will be tagged
v6.66.3— this repo has been publishing without git anchors, which is what made "what is unreleased?" undiagnosable here in the first place.🤖 Generated with Claude Code