chore(builtins): pin uutils revision as single source of truth#1537
Merged
chore(builtins): pin uutils revision as single source of truth#1537
Conversation
Adds `UUTILS_REVISION: &str = "<rev>"` in `crates/bashkit/src/builtins/generated/mod.rs` as the single source of truth for the uutils version that: - The codegen tool (drift workflow checks out uutils@UUTILS_REVISION before regenerating <util>_args.rs). - The body-drift harness (drift workflow builds the coreutils multicall from the same rev). - `just regen-coreutils-args` (reads the pin and checks out the local uutils clone at it before regenerating). Static invariant test in builtins/mod.rs walks generated/*_args.rs and asserts every header references the pinned rev. Manual partial regenerations that forget to bump (or mis-bump) the pin fail in CI before review. Drift workflow now runs against upstream HEAD and atomically bumps UUTILS_REVISION together with the regenerated files in one PR — args codegen and body-drift gate never diverge across an auto-PR boundary. The PR body shows the old-vs-new pinned rev so reviewers see the bump. Justfile `regen-coreutils-args` reads the pin and discovers utils from the manifest (every `pub mod <util>_args;` line), so adding a new util is one edit in `generated/mod.rs`. Pre-bump rev for cat/tac was `c23dc67` (POC). Regenerated at the current pinned rev `39364b6`; only header lines change — no semantic drift in the generated output. Spec: coreutils-args-port.md gains "Source-of-truth uutils revision pin" subsection and the CI-guard description tracks the new flow. Closes the source-of-truth pin acceptance item from #1530. Part of #1530.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 072a86a | Commit Preview URL Branch Preview URL |
May 05 2026, 08:27 PM |
This was referenced May 5, 2026
chaliy
added a commit
that referenced
this pull request
May 6, 2026
Minor release `0.4.1` → `0.5.0`. Two new builtins (`shuf`, `truncate`), a coreutils-codegen pipeline that ports uutils' `uu_app()` clap definitions for `cat`/`tac`/`truncate`/`shuf`/`readlink`, and `tool_def` flag-syntax improvements. ## Highlights - **Coreutils argument surface via codegen** — Ports uutils' `uu_app()` clap definitions into bashkit so builtins share the real coreutils argument shape; `cat`, `tac`, `truncate`, `shuf`, and `readlink` now flow through this surface, with a coreutils differential testing harness to catch parity drift. Pipeline reads a single pinned uutils revision so generated builtins, the differential harness, and CI all agree on the upstream source of truth (#1529, #1535, #1536, #1537, #1538, #1542). - **Site updates** — Bashkit agent skill is now published on the site, alongside rustdoc guides and content signal declarations for discoverability. ## What's Changed * refactor(builtins): migrate readlink to codegen-ported argument surface (#1542) * chore(site): publish bashkit agent skill (#1541) * chore(site): declare content signals * docs(site): publish rustdoc guides * feat(builtins): add shuf via codegen with helper-fn inlining (#1538) * chore(builtins): pin uutils revision as single source of truth (#1537) * feat(builtins): add truncate via codegen-ported argument surface (#1536) * test(builtins): add coreutils differential testing harness (#1535) * feat(builtins): port uutils argument surfaces via codegen (POC: cat, tac) (#1529) * feat(tool_def): accept --flag key=value... syntax for object/array flags (#1528) * fix(tool_def): coerce stringified JSON for array/object flag schemas (#1527) ## Publish-readiness report Per the updated `specs/release-process.md`: - [x] `cargo fmt --check` clean - [x] `cargo clippy --all-targets --all-features -- -D warnings` clean - [x] `cargo build` clean - [x] Versions synced across `Cargo.toml`, `crates/bashkit-cli/Cargo.toml`, `crates/bashkit-js/package.json`, `package-lock.json`, `Cargo.lock` - [x] `cargo publish --dry-run -p bashkit --allow-dirty` (after CI's monty-strip): **success** - [x] `cargo publish --dry-run -p bashkit-cli`: blocked only on ordering (`bashkit 0.5.0` not yet on crates.io) — resolves at real publish time when `publish-bashkit` runs first per `publish.yml`'s `needs:` chain. - [x] New `0.5.0` > latest published versions on crates.io / PyPI / npm (`0.4.1`). ## Companion change This branch also includes `chore(specs): document publish verification and post-merge monitoring`, codifying the verify-before-tag and watch-after-merge flow that this release follows. On merge, `release.yml` will create the GitHub Release `v0.5.0` and dispatch publish workflows for crates.io, PyPI, npm, and Homebrew. **Full Changelog**: v0.4.1...v0.5.0 --- _Generated by [Claude Code](https://claude.ai/code/session_01SvuLdA8pMAmP4woG2HqxKw)_
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.
Summary
Closes the source-of-truth uutils revision pin acceptance item
from #1530. Adds
pub const UUTILS_REVISION: &str = "<rev>"incrates/bashkit/src/builtins/generated/mod.rsas the single revshared across:
bashkit-coreutils-portcodegen tool (drift workflow checksout uutils at this rev before regenerating
<util>_args.rs).coreutils_differential_testsbody-drift harness (driftworkflow builds the
coreutilsmulticall from the same rev).just regen-coreutils-args(reads the pin and checks out thelocal uutils clone at it before regenerating).
Why
Before this PR, the args drift workflow used
uutils@HEADand thenew body-drift harness used a separately-installed
coreutilsbinarywith no version coordination. Reviewing an auto-PR meant guessing
which uutils rev a given divergence applied to. With the pin, the
two checks always run against the same upstream state.
Static invariant
builtins::tests::generated_args_headers_match_pinned_uutils_revisionwalks
generated/*_args.rsand asserts every header references thepinned rev. A manual partial regeneration that forgets to bump (or
mis-bumps) the pin fails in CI before review.
Drift workflow
Now runs against upstream HEAD and atomically bumps
UUTILS_REVISIONtogether with the regenerated files in one PR — args codegen and
body-drift gate never diverge across an auto-PR boundary. The PR body
shows the old-vs-new pinned rev so reviewers see the bump.
Pre-bump rev for cat/tac
Was
c23dc67(POC). Regenerated at the current pinned rev39364b6;only header lines change — no semantic drift in the generated output.
Test plan
cargo test -p bashkit --lib builtins::tests— green; newgenerated_args_headers_match_pinned_uutils_revisiontestpasses.
cargo clippy -p bashkit --all-targets --all-features -- -D warnings— green.cargo fmt --check— green.Scope
Part of #1530. The remaining acceptance item (per-flag diffcoverage for tac flipping from
diff_reasonrows to real assertionsas
tac -b/-r/-sare implemented) follows when those flags land.Generated by Claude Code