Fix release version derivation; add get-version CLI commands#31
Merged
Conversation
The headline version came from `unique | .[0]`, i.e. the lowest package version. Under lockstep versioning a release that bumps only a sub-package (dkjson 0.7.1 while the namesake stays 0.7.0) resolved to an already-released version and the release step silently no-op'd. Resolve one headline version as the semver max of the source channel and use it for both the release tag and the bundle asset name, so they can't disagree. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
report a feed channel's highest version or its distinct package versions.
Contributor
Test results — macos-latest ✅1060 · ubuntu-latest ✅1060 · windows-latest ✅1057Summary
🎉 No failed tests in this run. Github Test Reporter by CTRF 💚 |
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.
Two related release-tooling changes:
Fix the release-version derivation. The workflow picked the lowest package version (
unique | .[0]), so a lockstep release that bumps only a sub-package (dkjson while the namesake stays put) resolved to an already-released tag and silently cut nothing. It now resolves the semver max of the source channel, shared by the release tag and the bundle asset name so they can't disagree.Add
get-version/get-current-versionsCLI commands, backed by newUpdateFeedversion queries (getHighestVersionOnChannel,getVersionsOnChannel,getPackageVersionOnChannel), and use them to retire the version-derivingjqin the reusable publish workflow. Adds a configurabletag-prefixinput and factors the shared tag-naming intotag_name/emit_tagshelpers. Includes unit tests;l0.DependencyControlandl0.dkjsonare staged for the v0.8.0 release.🤖 Generated with Claude Code