moq-ffi: bump to 0.2.14#1505
Conversation
Manual patch bump so the new Swift release pipeline from #1502 gets exercised on the next moq-ffi-v* tag. release-plz cannot detect source changes for binary-only crates, so this has to be done by hand. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
WalkthroughThis PR bumps the moq-ffi package version from 0.2.13 to 0.2.14. The Cargo.toml manifest is updated with the new version, and a corresponding changelog entry is added documenting a Swift CI change that decouples the release manifest from the development Package.swift and gates publish on SPM resolve. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches✨ Simplify code
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 |
Summary
moq-ffifrom0.2.13to0.2.14.moq-ffi-v*tag so the new Swift release pipeline from #1502 (decoupled release manifest, SPM-resolve gate on publish) gets exercised end-to-end.Why manual
release-plzonly detects API/source changes viacargo semver-checks, which doesn't inspect binary-only crates.moq-ffiiscdylib/staticlib, so pure CI/packaging changes never trigger an automatic bump and the new Swift workflow would otherwise sit unrun until the next unrelated source change.Test plan
just rs releaseproduces amoq-ffi-v0.2.14tag.release-swift.ymlruns against that tag and the SPM-resolve gate passes before publish.(Written by Claude)
🤖 Generated with Claude Code