Skip to content

chore(main): release 0.0.23#579

Merged
ewhauser merged 2 commits intomainfrom
release-please--branches--main--components--shuck
Apr 26, 2026
Merged

chore(main): release 0.0.23#579
ewhauser merged 2 commits intomainfrom
release-please--branches--main--components--shuck

Conversation

@ewhauser
Copy link
Copy Markdown
Owner

@ewhauser ewhauser commented Apr 25, 2026

🤖 I have created a release beep boop

0.0.23 (2026-04-26)

Features

  • cli: support per-file shell overrides (#608) (fbfe3e2)

Bug Fixes

  • linter: align S001 indirect expansion parity (#596) (6341fc9)
  • linter: align S001 safe optional values (#594) (7575800)
  • linter: clear S001 initializer self-reference divergences (#598) (2f7b5d7)
  • linter: generalize C006 build-flag parity (#580) (ff1c1dc)
  • linter: generalize xargs inline replace parity (#581) (6ac42f2)
  • linter: move C005 exemptions into facts (#583) (77b6028)
  • linter: share shell dialect parsing policy (#600) (925b6c4)
  • linter: stop ambient contracts initializing runtime names (#582) (4ec1349)
  • website: keep rule docs in sync (#607) (c687090)

Performance

  • linter: avoid sorting command fact relationships (#590) (789d785)
  • linter: cache C133 builtin array history (#602) (697b6b1)
  • linter: index C063 activation windows (#597) (8954525)
  • linter: index possible misspelling candidates (#603) (1e6ba31)
  • linter: reduce facts allocation churn (#584) (b7cbee1)
  • linter: reduce facts-layer allocation churn (#578) (f0a282f)
  • linter: reuse command relationships in facts (#592) (585bbe9)
  • linter: reuse command relationships in more facts (#593) (e0b8708)
  • semantic: avoid eager reaching map materialization (#591) (22fe078)
  • semantic: index parameter guard flow refs (#605) (d6bb74d)
  • semantic: reduce CFG allocation churn (#587) (1e66db0)
  • speed up large corpus hotspot analysis (#585) (1fc11ae)

Documentation

Refactor

  • formatter: replace formatter implementation with stubs (#588) (800d9f3)

This PR was generated with Release Please. See documentation.

@ewhauser ewhauser added the autorelease: pending Tracks pending release-please PRs label Apr 25, 2026
@ewhauser ewhauser changed the title chore(main): release 0.0.11 chore(main): release 0.0.23 Apr 25, 2026
@ewhauser ewhauser force-pushed the release-please--branches--main--components--shuck branch from 31d2ca1 to e18c214 Compare April 25, 2026 17:00
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 039ca5b2c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread Cargo.toml Outdated

[workspace.package]
version = "0.0.22"
version = "0.0.11"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Bump workspace version forward from 0.0.22

This release commit moves workspace.package.version (and all internal crate dependency pins) backward from 0.0.22 to 0.0.11, which makes the new release semver-older than the currently advertised latest. In practice, consumers resolving the highest version will continue to get 0.0.22, so fixes included in this release will not be picked up as the newest artifact, and publishing can also collide with previously used 0.0.11 versioning.

Useful? React with 👍 / 👎.

Comment thread .release-please-manifest.json Outdated
@@ -1,3 +1,3 @@
{
".": "0.0.22"
".": "0.0.11"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep release-please manifest at the latest version

The manifest is reset from 0.0.22 to 0.0.11, so subsequent release-please runs will calculate releases from an older base and can regenerate already-used version ranges (as reflected by the reversed changelog compare range v0.0.22...v0.0.11). That can break automated tagging/version progression and should be kept monotonic with the latest released version.

Useful? React with 👍 / 👎.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 25, 2026

Macro CLI Benchmark Deltas

Compared ff5a07c against macro CLI baseline 239f4c8.

Positive deltas mean slower shuck check --no-cache runs.

  • Baseline source: downloaded from the latest successful main CI artifact
  • Baseline preparation: success
  • Comparison run: success
  • Workflow run: details

Aggregate

Benchmark Baseline Head Delta
all 264.12 ms +/- 8.42 ms 250.13 ms +/- 7.19 ms -5.29%

Flagged aggregate regressions over +5.0%: 0

Per-fixture macro deltas
Benchmark Baseline Head Delta
all 264.12 ms +/- 8.42 ms 250.13 ms +/- 7.19 ms -5.29%
bashtop 190.87 ms +/- 1.79 ms 177.36 ms +/- 5.27 ms -7.08%
fzf-install 11.81 ms +/- 306.93 us 10.93 ms +/- 169.55 us -7.47%
homebrew-install 22.16 ms +/- 320.73 us 21.49 ms +/- 524.40 us -3.03%
nvm 154.53 ms +/- 2.91 ms 140.50 ms +/- 2.07 ms -9.08%
pyenv-python-build 75.66 ms +/- 4.16 ms 66.80 ms +/- 1.34 ms -11.71%
ruby-build 42.65 ms +/- 1.38 ms 40.52 ms +/- 963.25 us -5.01%
Largest changes

Improvements

Benchmark Baseline Head Delta
pyenv-python-build 75.66 ms +/- 4.16 ms 66.80 ms +/- 1.34 ms -11.71%
nvm 154.53 ms +/- 2.91 ms 140.50 ms +/- 2.07 ms -9.08%
fzf-install 11.81 ms +/- 306.93 us 10.93 ms +/- 169.55 us -7.47%
bashtop 190.87 ms +/- 1.79 ms 177.36 ms +/- 5.27 ms -7.08%
all 264.12 ms +/- 8.42 ms 250.13 ms +/- 7.19 ms -5.29%
Non-zero benchmark exit codes
  • all baseline exit codes: 1,1,1,1,1,1,1,1,1,1; head exit codes: 1,1,1,1,1,1,1,1,1,1
  • bashtop baseline exit codes: 1,1,1,1,1,1,1,1,1,1; head exit codes: 1,1,1,1,1,1,1,1,1,1
  • fzf-install baseline exit codes: 1,1,1,1,1,1,1,1,1,1; head exit codes: 1,1,1,1,1,1,1,1,1,1
  • nvm baseline exit codes: 1,1,1,1,1,1,1,1,1,1; head exit codes: 1,1,1,1,1,1,1,1,1,1
  • pyenv-python-build baseline exit codes: 1,1,1,1,1,1,1,1,1,1; head exit codes: 1,1,1,1,1,1,1,1,1,1

@ewhauser ewhauser force-pushed the release-please--branches--main--components--shuck branch 24 times, most recently from 1badfee to 51c616d Compare April 26, 2026 03:26
@ewhauser ewhauser force-pushed the release-please--branches--main--components--shuck branch from 59490a0 to 0d525b6 Compare April 26, 2026 03:28
@ewhauser ewhauser merged commit 96d1274 into main Apr 26, 2026
19 checks passed
@ewhauser ewhauser deleted the release-please--branches--main--components--shuck branch April 26, 2026 04:09
@ewhauser
Copy link
Copy Markdown
Owner Author

🤖 Created releases:

🌻

@ewhauser ewhauser added autorelease: tagged Tracks release-please PRs whose tag has been created and removed autorelease: pending Tracks pending release-please PRs labels Apr 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged Tracks release-please PRs whose tag has been created

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant