Skip to content

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

Draft
galargh wants to merge 14 commits into
masterfrom
galargh/release-test
Draft

test: multi-crate release v4.7.6#2267
galargh wants to merge 14 commits into
masterfrom
galargh/release-test

Conversation

@galargh

@galargh galargh commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

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-check correctly runs cargo publish --workspace --dry-run and succeeds.

@github-project-automation github-project-automation Bot moved this to 📌 Triage in FilOz Mar 18, 2026
@codecov-commenter

codecov-commenter commented Mar 18, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files

Impacted file tree graph

@@           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:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@galargh galargh added the release Force release when not targeting the default branch label Mar 18, 2026
- 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
galargh force-pushed the galargh/release-test branch from 6385bc3 to 3f83863 Compare March 18, 2026 21:34
@galargh
galargh marked this pull request as draft March 18, 2026 21:50
@galargh
galargh force-pushed the galargh/release-test branch from 9d33b23 to 5420a08 Compare March 26, 2026 11:33
@github-actions

Copy link
Copy Markdown

Suggested tag: fvm_sdk@v4.7.6

Comparing to: fvm_sdk@v4.7.5 (diff)

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

@github-actions

Copy link
Copy Markdown

Suggested tag: fvm_integration_tests@v4.7.6

Comparing to: fvm_integration_tests@v4.7.4 (diff)

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

@github-actions

Copy link
Copy Markdown

Suggested tag: fvm_shared@v4.7.6

Comparing to: fvm_shared@v4.7.5 (diff)

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

@github-actions

Copy link
Copy Markdown

Suggested tag: fvm@v4.7.6

Comparing to: fvm@v4.7.5 (diff)

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

Base automatically changed from galargh/release to master April 16, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Force release when not targeting the default branch

Projects

Status: 📌 Triage

Development

Successfully merging this pull request may close these issues.

2 participants