network@version for single variants #468
Merged
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.
This pull request updates the logic for generating git tags during the GitHub release process, especially for multi-variant packages. The main improvement is that the
getNextGitTagfunction now consistently uses thevariant@v<version>format for all multi-variant releases, even if there is only one variant. This change ensures more predictable and uniform tag naming. The update also propagates the newisMultiVariantparameter through the relevant release tasks.Release tag generation improvements:
getNextGitTagingetNextGitTag.tsto accept anisMultiVariantparameter and always use thevariant@v<version>format for multi-variant packages, even with a single variant. The fallback for legacy behavior is preserved ifisMultiVariantis not set.getHandleTagsTaskandgetCreateReleaseTaskto accept and pass theisMultiVariantparameter, ensuring consistent tag generation throughout the release process. [1] [2] [3] [4]