release playbook: enforce release tagging policy #518
Merged
Conversation
This file contains 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
gotmax23
changed the title
|
Okay, this should be ready for review |
gotmax23
force-pushed
the
validate-tags-block
branch
2 times, most recently
from
efba57a to
cefe4be
Compare
felixfontein
approved these changes
May 2, 2023
gotmax23
force-pushed
the
validate-tags-block
branch
from
cefe4be to
2135522
Compare
|
I force pushed to add a changelog frag |
- ansible >= 7.2.0 and < 9.0.0a1 -- the playbook will validate the tags file and *warn* but not *error* for violating collections. - ansible >= 9.0.0a1 -- the playbook will treat violations as errors.
gotmax23
force-pushed
the
validate-tags-block
branch
from
2135522 to
361f070
Compare
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.
Relates: ansible-community/ansible-build-data#222