Repository navigation
feat: configurable tag format for version-workspace - #35
Merged
Merged
Conversation
Version AnalysisNext Version: Changelog: 📄 View detailed changelog in job summary Badge: |
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.
version-workspace hardcodes its tag format to
{package}/v{version}. Repos that were previously versioned with melos have tags likemy_pkg-v1.2.3, so the tool finds no previous refs there and you have to seed duplicate tags in the new format before it picks anything up.This adds a
--tag-formatoption that controls both how existing tags are looked up and how new ones are created:mtrust_api_guard version-workspace --tag-format "{package}-v{version}"The format must contain
{package}and end with{version}. Default stays{package}/v{version}, so nothing changes for existing setups. Tag matching is still lenient about thevprefix, same as before.Covered by a unit test for the format parsing and an end to end test that versions a workspace against melos style tags.