Repository navigation
Create draft GitHub release automatically when a v* tag is pushed - #58
Merged
Merged
Conversation
- buildfile: derive toolbox version from TOOLBOX_VERSION, else the latest vX.Y.Z git tag; error if neither is available. - CI: set TOOLBOX_VERSION from the tag, fetch full history in package so branch builds can find tags, and add a release job that verifies the tagged commit is on main before publishing the .mltbx. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Published releases are immutable, so CI creates a draft with the .mltbx attached and writes its SHA-256 to the job summary. An admin verifies the asset digest and publishes the draft from the GitHub UI. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Collaborator
|
looks good. no flags |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
(Closed and reopened since GitHub wasn't picking up the latest commit.) |
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
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.
Summary
Pushing a
vX.Y.Ztag now builds the toolbox and creates a draft GitHub Release with the.mltbxattached. An admin reviews and publishes the draft.Release process
test→package→release. The release job checks the tagged commit is onmain, then creates a draft Release with auto-generated notes and writes the.mltbxSHA-256 to the job summary.Changes
buildfile.m:mltbxreads the toolbox version fromTOOLBOX_VERSION, falling back to the latestvX.Y.Zgit tag. The build errors (buildfile:NoToolboxVersion) if neither is available, instead of packaging a stale hardcoded version..github/workflows/matlab.yml:packagesetsTOOLBOX_VERSIONfrom the tag on tag builds, and checks out withfetch-depth: 0so branch builds can find tags.releasejob (only onv*tags, aftertestandpackagepass) checks that the tagged commit is onmain, then creates the draft Release.CONTRIBUTING.md: new "Releasing" section documenting the admin-only release process.Safety
pull_request, so fork runs get a read-only token and no secrets.Testing
buildtool mltbx: version 0.1.4 from the git tag, 9.9.9 whenTOOLBOX_VERSION=9.9.9, and the expected error when git is unavailable.v0.1.4, fails for a commit not onmain.🤖 Generated with Claude Code