Bump gitsemver to v2.0.0 in create-release workflow - #199
Merged
Conversation
gitsemver v2.0.0 renamed the `version` subcommand to `get`. devctl v8.3.1 updated generated Makefiles to use `gitsemver get`, which fails with v1.1.2, leaving VERSION empty and producing misnamed tarballs that the upload step cannot find.
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.
What
Bump the pinned
gitsemverversion from1.1.2to2.0.0in the build-artifacts job ofcreate-release.yaml.Why
gitsemverv2.0.0 (released 2026-06-02) renamed theversionsubcommand toget.devctlv8.3.1 updated itsgen makefileoutput to callgitsemver get, and devctl's own Makefile was regenerated with that change.With
gitsemver1.1.2 still pinned here, the build step exits with:VERSIONis left empty, the tarball is nameddevctl-v-<platform>.tar.gzinstead ofdevctl-v<X.Y.Z>-<platform>.tar.gz, andgh release uploadfails withno such file or directory.Any repo that has already regenerated its Makefile with devctl ≥ v8.3.1 will hit the same failure until this is merged.