Skip to content

chore: prepare release v0.3.6 - #128

Merged
frankieramirez merged 3 commits into
mainfrom
cast/release-0.3.6
Oct 7, 2026
Merged

frankieramirez merged 3 commits into
mainfrom
cast/release-0.3.6

Conversation

@frankieramirez

@frankieramirez frankieramirez commented Oct 7, 2026 •

Copy link
Copy Markdown
Owner

Prepare Bushel 0.3.6 with the merged audit fixes. Cargo.toml and Cargo.lock change the application version and replace yanked chacha20 0.10.1 with 0.10.2; structural comparison against current main verifies every other package version and dependency edge is preserved. A separate integration correction fixes ASCII health-banner punctuation with regression tests.

Integrated main: 0f24599 (PR119, PR125, PR126 and PR127).
Final head: ba7e1ae.
Final tree: ca20bb65a0140ff656724ee03c8cbe4d1abb4bd6.
Integration commit 9088e0d preserves published release ancestry with parents 3ef3a04 and 0f24599.

Proposed release notes

All four audit PRs are merged and included. Compatibility claims and TESTED_* ranges remain unchanged. Native stopped-container backlog retrieval and macOS 27 support are not claimed.

Regression and validation

The independent coordinator review found stats banners' middle dot and resource-read banners' em dash/middle dot bypassed Theme. Four new render tests failed against the integrated source before the fix (stats, images, volumes, networks). The fix converts only application-owned suffixes through Theme::chrome, leaving external gists untouched. All 24 UI interaction tests then pass, including the external Unicode preservation test. Cases cover Rail/Table at 55x20 and 120x40.

Full exact-head checks passed from a clean checkout with an isolated build target:

  • cargo fmt --check
  • cargo clippy --locked --all-targets -- -D warnings
  • cargo test --locked: 362 passed (209 library, 11 binary, 90 engine, 10 quit, 10 read ownership, 2 README, 6 stop attribution, 24 UI interaction)
  • docs/schema/keymap/config checks; docs version 0.3.6
  • generated man page and Bash/Zsh/Fish completions; nonempty/content checks and Bash syntax
  • binary version: bushel 0.3.6
  • cargo publish --dry-run --locked: package verified, no yanked warning, no upload
  • official cargo-dist 0.32.0 dist plan --tag=v0.3.6: stable release, expected ARM archive/installers/assets/checksums
  • clean source/head/tree and final four-file diff; precise lock invariants

Remote CI passed on the exact final head: https://github.com/frankieramirez/bushel/actions/runs/37610809782 — macOS fmt/clippy/test and Linux docs/assets/publish dry-run jobs all completed successfully. Release planning passed: https://github.com/frankieramirez/bushel/actions/runs/37610810205. CodeRabbit status is success.
Evidence: /tmp/bushel-release-final-ba7e1ae and /tmp/bushel-release-final-9088e0d/health-banners-{red,green}.txt.

Release controls and limits

Draft only. Coordinator reviews the final version PR and explicitly directs tagging/publication. No tag, release, actual cargo upload or deploy hook invocation was performed.

PR events plan only; tag pushes publish. Existing HOMEBREW_TAP_TOKEN is required to update the tap before announcement. BUSHEL_SH_DEPLOY_HOOK absence fails site deployment. CARGO_REGISTRY_TOKEN absence silently skips crates.io upload; same-version manual publication is then required. No credentials or repository settings are created or changed here.

Linux cloud verification cannot exercise Apple Containers virtualization or real interactive terminal restoration. Physical/self-hosted Apple silicon validation is mandatory before expanding the tested CLI range or claiming macOS 27 support. Existing cloud GitHub CLI GH_TOKEN is invalid; connector writes and git work.

Summary by CodeRabbit

  • Bug Fixes

    • Health banners now format log hints and last-good-state messages consistently across layouts.
  • Tests

    • Expanded coverage for health banners across resource types, layouts, terminal sizes, and ASCII and Unicode error messages.

Bump Bushel and replace yanked chacha20 0.10.1 with 0.10.2 without other dependency changes.
@coderabbitai

coderabbitai Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 251b1105-90ec-4bca-9df3-42b109398deb
📥 Commits

Reviewing files that changed from the base of the PR and between 0f24599 and ba7e1ae.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • Cargo.toml
  • src/ui/draw.rs
  • tests/ui_interaction.rs

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The package version changes from 0.3.5 to 0.3.6. Health-banner hints now use the chrome formatter. Interaction tests cover the banners across panes, layouts, sizes, and error text.

Changes

Health Banner Formatting

Layer / File(s) Summary
Banner formatting and coverage
src/ui/draw.rs, tests/ui_interaction.rs, Cargo.toml
The stats-unavailable and list-failure banners format their hints through th.chrome. Interaction tests check banner text across panes and layouts at two sizes, including ASCII and Unicode errors. The package version changes to 0.3.6.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to ba7e1

The reviewed changes are mergeable after normal checks; no concrete current-head risk remains identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 2 files. (1 skipped: 1… Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the 0.3.6 release preparation and matches the version update and release-focused changes.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 9 functions across 2 files. (1 skipped: 1 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the banner glow,
The hints now wear their chrome just so.
Through panes and sizes, tests take flight,
ASCII and Unicode read right.
The rabbit hops, pleased with the show.

Comment @coderabbitai help to get the list of available commands.

Preserve published release ancestry and the two-file version/chacha20 diff.
Preserve external Unicode errors while converting application-owned stats and resource-read banner suffixes. Cover stats, images, volumes and networks in both layouts at floor and wide sizes.
@frankieramirez
frankieramirez marked this pull request as ready for review October 7, 2026 11:01
@frankieramirez
frankieramirez merged commit 5f42111 into main Oct 7, 2026
13 checks passed
@frankieramirez
frankieramirez deleted the cast/release-0.3.6 branch October 7, 2026 11:05
@frankieramirez frankieramirez mentioned this pull request Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant