test: multi-crate release v4.7.6 - #2267
Conversation
Co-authored-by: Steve Loeppky <biglep@filoz.org>
- Update release-check.yml to use 'cargo publish --workspace --dry-run' - Update releaser.yml to automate 'cargo publish --workspace' on merge - Update CONTRIBUTING.md to reflect the new automated process and remove outdated limitations
…-workflows # Conflicts: # CONTRIBUTING.md
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2267 +/- ##
=======================================
Coverage 77.02% 77.02%
=======================================
Files 143 143
Lines 14187 14187
=======================================
Hits 10927 10927
Misses 3260 3260 🚀 New features to boost your workflow:
|
- Enable OIDC trusted publishing for crates.io (id-token: write) - Use --no-default-features for cargo publish to avoid OpenCL dependency - Update release documentation to reflect these changes
6385bc3 to
3f83863
Compare
9d33b23 to
5420a08
Compare
|
Suggested tag: Comparing to: fvm_sdk@v4.7.5 (diff) Automatically created GitHub ReleaseA draft GitHub Release has been created. |
|
Suggested tag: Comparing to: fvm_integration_tests@v4.7.4 (diff) Automatically created GitHub ReleaseA draft GitHub Release has been created. |
|
Suggested tag: Comparing to: fvm_shared@v4.7.5 (diff) Automatically created GitHub ReleaseA draft GitHub Release has been created. |
|
Suggested tag: Comparing to: fvm@v4.7.5 (diff) Automatically created GitHub ReleaseA draft GitHub Release has been created. |
This is a test PR to verify the workspace-aware release automation.
It bumps the workspace version to
4.7.6, which affects multiple interdependent crates (fvm,fvm_shared,fvm_sdk,fvm_integration_tests).The goal is to verify that
release-checkcorrectly runscargo publish --workspace --dry-runand succeeds.