ci: update codemeta.json through the shared release workflow - #198
Merged
Merged
Conversation
matbox-actions v1.7 updates codemeta.json inside the packaging job and stages it in the release check-in commit, before the tag moves. The repo-local job and MATLAB task did the same work in a second commit after tagging, so the tag carried stale metadata. Both are removed. releaseNotes now links to the release's tag page. Anchors on the releases list stop working once a release ages off the first page. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Test Results (R2022a)858 tests 854 ✅ 4m 46s ⏱️ Results for commit 26c2842. |
Contributor
Test Results (R2026a)858 tests 856 ✅ 4m 27s ⏱️ Results for commit 26c2842. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #198 +/- ##
==========================================
- Coverage 80.37% 80.10% -0.28%
==========================================
Files 424 424
Lines 4403 4423 +20
==========================================
+ Hits 3539 3543 +4
- Misses 864 880 +16 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow calls the matbox-actions
prepare-release-workflowat@v1. Since matbox-actions v1.7, its packaging job updatescodemeta.jsonand stages it in the "Final check-ins" commit before the tag is moved, so the tagged source carries metadata for the released version.The repo-local
update-codemetajob and theupdateCodeMetaFileMATLAB task did the same work in a separate commit after tagging. For v0.12.0 that left the tag pointing at a codemeta.json still describing 0.11.0. Both are removed here. The shared step reads the minimum MATLAB release fromtools/MLToolboxInfo.json, so nothing else in this repo needs to change.releaseNotesincodemeta.jsonnow links to the release's tag page, which is what the shared step writes. The previous anchor on the releases list stops working once a release ages off the first page, which already affects v0.9.0.🤖 Generated with Claude Code