automation: splitting the determining and publishing of the Git Tag #834
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 is needed as a part of hashicorp/pandora#3601 since we're going to be publishing multiple Go Modules at different paths - but the version number of each of them is going to be the same.
As such this PR splits the determining and publishing of the Git Tag - such that the existing update tooling continues to work with minor changes (tracked in hashicorp/terraform-provider-azurerm#24602).
Given this is a Github Action this is hard to test locally - I've tested the scripts (which are fine) - but I suspect this change should be fine to merge today, prior to enabling module support.