chore: revive and improve release automation by galargh · Pull Request #2266 · filecoin-project/ref-fvm

galargh · 2026-03-18T20:10:52Z

This PR revives the release automation effort from #2027 with several key improvements:

Workspace-Aware Dry-Run: Updated release-check.yml to use cargo publish --workspace --dry-run. This leverages Cargo 1.90+'s native multi-package publishing to correctly verify the entire dependency graph, solving the previous failure with interdependent crates.
Automated Publishing: Updated releaser.yml to include a cargo publish --workspace step. This automates the final push to crates.io upon merge, ensuring crates are published in the correct order.
Updated Documentation: Refreshed RELEASE.md to reflect the new automated process and cleaned up CONTRIBUTING.md to match the current project structure.
Merge Master: Incorporated the latest changes from master, including the transition of release documentation to its own file.

Test Plan

To verify these changes, we will perform a live test by simulating a multi-crate release:

Create a Test PR: Open a new PR targeting the galargh/release branch.
Version Bumps: In the test PR, bump the versions of fvm_shared, fvm, and fvm_sdk simultaneously in Cargo.toml.
Verify Release Checker:
- Ensure the release-check workflow triggers correctly.
- Verify that the Dry-run publish step (cargo publish --workspace --dry-run) passes.
- Crucial Check: This should succeed even though the new versions of the dependencies are not yet on crates.io, confirming that Cargo's native workspace-aware publishing is correctly resolving internal dependencies.
Validation: Check that the draft GitHub Releases are correctly created for each crate.

Checklist:

✅ test: multi-crate release v4.7.6 #2267

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-commenter · 2026-03-18T20:15:20Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.02%. Comparing base (a29674a) to head (f8f80dd).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2266   +/-   ##
=======================================
  Coverage   77.02%   77.02%           
=======================================
  Files         143      143           
  Lines       14187    14187           
=======================================
  Hits        10927    10927           
  Misses       3260     3260

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

- 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

.github/workflows/release-check.yml

galargh · 2026-03-18T21:53:21Z

.github/workflows/releaser.yml

+
+permissions:
+  contents: write
+  id-token: write


We should verify that this workflow is listed as a trusted publisher in crates.io.

I'd look but I can't find the crate settings even though I should be in the team that has publish access, crates.io teams is janky, maybe @hanabi1224 || @LesnyRumcajs has a clue

Settings should be next to Security on crates.io ,however, I don't have the setting permission of fvm* crates either

https://crates.io/crates/fvm/settings
https://crates.io/crates/fvm_integration_tests/settings
https://crates.io/crates/fvm_sdk/settings
https://crates.io/crates/fvm_shared/settings

Should any other crates be modified?

I think:

https://crates.io/crates/fvm_ipld_amt/settings

https://crates.io/crates/fvm_ipld_hamt/settings

https://crates.io/crates/fvm_ipld_kamt/settings

https://crates.io/crates/fvm_ipld_car/settings

https://crates.io/crates/fvm_ipld_blockstore/settings

https://crates.io/crates/fvm_ipld_bitfield/settings

https://crates.io/crates/fvm_ipld_encoding/settings

I think:

https://crates.io/crates/fvm_ipld_amt/settings

https://crates.io/crates/fvm_ipld_hamt/settings

https://crates.io/crates/fvm_ipld_kamt/settings

https://crates.io/crates/fvm_ipld_car/settings

https://crates.io/crates/fvm_ipld_blockstore/settings

https://crates.io/crates/fvm_ipld_bitfield/settings

https://crates.io/crates/fvm_ipld_encoding/settings

I did the same setup for those as well - my bad for missing those previously.

BigLep · 2026-03-19T07:21:36Z

Added @LesnyRumcajs as another maintainer who may be able to get to looking at this sooner.

LesnyRumcajs · 2026-03-19T19:18:12Z

I'm OOO until Tuesday, best bet is @hanabi1224 now, I guess!

rvagg · 2026-03-20T07:01:53Z

worth a try! wouldn't harm to push through a release or three

this has to also work for v3 and v4 so I guess we'd backport it to there as well?

galargh · 2026-03-24T09:14:36Z

this has to also work for v3 and v4 so I guess we'd backport it to there as well?

Yes, I don't see why not. I would test it in the default branch first and then do the backport if everything works as expected.

BigLep · 2026-03-24T23:32:51Z

What are the next steps? Do we just need to try it out?

galargh · 2026-03-26T11:38:56Z

Yes, I did the testing we can do without doing a proper release in #2267

BigLep · 2026-03-30T00:39:02Z

@LesnyRumcajs or @hanabi1224 : is there an upcoming proper release we can try this out with to validate it?

hanabi1224 · 2026-03-30T00:46:01Z

is there an upcoming proper release we can try this out with to validate it?

@BigLep I think #2268 needs a release. cc @rvagg

BigLep · 2026-03-31T04:54:05Z

Ok, so it seems like:

To test this out, we can do a release after chore(deps): bump wasmtime #2268 lands (but that PR requires some more careful investigation)
We need someone to look at the change and give review (independent of doing a relase with it). @LesnyRumcajs or @hanabi1224 : can you please take that?

LesnyRumcajs · 2026-03-31T07:25:02Z

@galargh Can you please help me understand why do we need two very similar workflows? I understand one is for checking the release and another for an actual release, but ideally there'd be just one with a dry_run param. Obviously, it's not a huge deal given the files are not that big and I wouldn't expect much development there to cause potential divergence.

.github/workflows/releaser.yml

.github/workflows/release-check.yml

galargh and others added 10 commits July 23, 2024 14:19

ci: automate creation of GitHub releases and tags

084c879

docs: update documentation on release creation

c0aa24f

feat: release individual packages

c4fa7c0

fix: trigger release workflows on Cargo.toml changes

2292bc1

chore: simplify cargo-publish job check

85586da

ci: limit duplication in release workflows

50273e3

docs: document the new release process and possible improvements

a3fb5a9

chore: apply suggestions from code review

423e826

Co-authored-by: Steve Loeppky <biglep@filoz.org>

Merge remote-tracking branch 'origin/master' into ipdx/unified-github…

8fa2fd8

…-workflows # Conflicts: # CONTRIBUTING.md

github-project-automation bot added this to FilOz Mar 18, 2026

github-project-automation bot moved this to 📌 Triage in FilOz Mar 18, 2026

chore: enable trusted publishing and fix OpenCL linkage

5d31a03

- 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

galargh commented Mar 18, 2026

View reviewed changes

.github/workflows/release-check.yml Outdated Show resolved Hide resolved

galargh commented Mar 18, 2026

View reviewed changes

galargh marked this pull request as ready for review March 18, 2026 21:54

galargh requested review from BigLep and rvagg March 18, 2026 21:54

BigLep requested a review from LesnyRumcajs March 19, 2026 07:21

BigLep moved this from 📌 Triage to 🔎 Awaiting Review in FilOz Mar 19, 2026

ci: install opencl in release workflows

ef9e20f

LesnyRumcajs reviewed Mar 31, 2026

View reviewed changes

.github/workflows/releaser.yml Outdated Show resolved Hide resolved

LesnyRumcajs reviewed Mar 31, 2026

View reviewed changes

.github/workflows/release-check.yml Outdated Show resolved Hide resolved

Apply changes requested in review

f8f80dd

LesnyRumcajs approved these changes Apr 13, 2026

View reviewed changes

github-project-automation bot moved this from 🔎 Awaiting Review to ✔️ Approved by reviewer in FilOz Apr 13, 2026

Conversation

galargh commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Plan

Uh oh!

codecov-commenter commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

galargh Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

rvagg Mar 20, 2026

Choose a reason for hiding this comment

Uh oh!

hanabi1224 Mar 20, 2026

Choose a reason for hiding this comment

Uh oh!

BigLep Mar 20, 2026

Choose a reason for hiding this comment

Uh oh!

galargh Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

BigLep Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

BigLep commented Mar 19, 2026

Uh oh!

LesnyRumcajs commented Mar 19, 2026

Uh oh!

rvagg commented Mar 20, 2026

Uh oh!

galargh commented Mar 24, 2026

Uh oh!

BigLep commented Mar 24, 2026

Uh oh!

galargh commented Mar 26, 2026

Uh oh!

BigLep commented Mar 30, 2026

Uh oh!

hanabi1224 commented Mar 30, 2026

Uh oh!

BigLep commented Mar 31, 2026

Uh oh!

LesnyRumcajs commented Mar 31, 2026

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

galargh commented Mar 18, 2026 •

edited

Loading

codecov-commenter commented Mar 18, 2026 •

edited

Loading