chore(release): bump version to 0.12.3-SNAPSHOT, rules baseline to 0.12.2 - #271
Conversation
…12.2 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: fortemate/dicechess-engine/.coderabbit.yaml Review profile: ASSERTIVE 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 |
Hacktron Security Check - SkippedReason: OSS PR review limit reached for this approved repository and developer. New OSS PRs for this repository will resume at the start of the next cycle.
|
|



Post-release bookkeeping for v0.12.1 and v0.12.2, opened manually after
Ops: Releasefailed on both cuts at the "Publish both packages to npmjs.org through the canonical workflow"
step (registry-integrity-propagation timeout in
.mise/lib/npm-publish-if-missing.sh), whichalso skipped the automatic "Create GitHub Release" and "Open the next-SNAPSHOT version-bump
pull request" steps for both releases.
What was already recovered manually, outside this PR:
@fortemate/dicechess-engine@0.12.1/-wasm@0.12.1and@0.12.2/-wasm@0.12.2arepublished on npmjs.org (verified via
npm view).and v0.12.2 were created
with the exact assets from each run's immutable npm release bundle artifact.
This PR does the one remaining piece: sets
build.sbtversion to0.12.3-SNAPSHOTsomaincarries the next development version, and moves
RulesMimaBaselineto0.12.2(the latestactual release) so the rules binary-compatibility gate compares against it. Nothing else changes.
Note: PR #266 already raised
NPM_VERIFY_MAX_ATTEMPTS/NPM_VERIFY_SLEEP_SECONDS(30s → 120s)in response to the v0.12.1 failure, but the v0.12.2 run still hit the same timeout — npm registry
propagation exceeded even the increased budget. Worth a follow-up (e.g. treat the propagation
check as non-fatal, since
npm publishitself already succeeded by that point).🤖 Generated with Claude Code