Repository navigation
fix: write the build number as semantic version metadata on R2026b - #74
Merged
Merged
Conversation
From R2026b, ToolboxOptions.ToolboxVersion must be a semantic version and rejects Major.Minor.Patch.Build (mpm:arguments:InvalidVersion). Earlier releases accept only that four-part form and reject Major.Minor.Patch+Build. packageToolbox adds a build number for the default "build" release type, so packaging failed on R2026b. createToolboxOptions now writes a four-part version as Major.Minor.Patch+Build on R2026b and later. The .mltbx file name turns "+" into "_", so it keeps the same form on every release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Test Results34 tests 31 ✅ 30s ⏱️ For more details on these failures, see this check. Results for commit 6a84255. ♻️ This comment has been updated with latest results. |
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.
From R2026b,
ToolboxOptions.ToolboxVersionmust be a semantic version and rejectsMajor.Minor.Patch.Build(mpm:arguments:InvalidVersion). Earlier releases accept only that four-part form and rejectMajor.Minor.Patch+Build.packageToolboxadds a build number for its default"build"release type, so packaging failed on R2026b. This is what fails the threepackageToolboxtests inTasksTest.createToolboxOptionsnow writes a four-part version asMajor.Minor.Patch+Buildon R2026b and later, and passes the version through unchanged on earlier releases. The.mltbxfile name turns+into_, so it keeps the formName_v0_11_0_1.mltbxon every release.Contents.mkeeps the four-part version.The R2026a and R2026b behaviour was observed in a probe run in github-actions-sandbox. MathWorks documents the change under "R2026b: ToolboxVersion must adhere to semantic version syntax" on the
matlab.addons.toolbox.ToolboxOptionspage.The
SetupTesttests also fail on R2026b, for a separate reason fixed in #73.🤖 Generated with Claude Code