chore(release): 0.12.1 - #234
Conversation
Closes the Unreleased section and bumps the workspace to 0.12.1. Patch: one compiler fix (#233). 0.12.0's plugin configuration check (E1023) judged env:// and file:// references as the values they stand for, so a spec reading a ws-upstream URL from the environment no longer compiled. The artifact format is unchanged, so 0.12.0 artifacts load as they are.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: barbacane-dev/barbacane/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
Closes the Unreleased section and bumps the workspace to 0.12.1.
Patch: one compiler fix, #233. 0.12.0's plugin configuration check (
E1023) judgedenv://andfile://references as the values they stand for, so a spec reading aws-upstreamURL from the environment stopped compiling. The artifact format is unchanged (still 7): 0.12.0 artifacts load as they are.Same footprint as the 0.12.0 release:
Cargo.toml(10 version fields),Cargo.lock(workspace crates only),CHANGELOG.md(section, headline, compare links). #232 is CI-only and has no user-facing entry.After merge: tag
v0.12.1on the merge commit; the release workflow checks the tag againstCargo.tomland the changelog.