-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare project for semi-pinned tags for major version #14
Prepare project for semi-pinned tags for major version #14
Conversation
037bf6c
to
e49a78d
Compare
.github/workflows/tag.yml
Outdated
@@ -3,13 +3,13 @@ name: Application Release | |||
on: | |||
push: | |||
tags: | |||
- "v*" | |||
- "v1.*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this change? If we ever make a v2 we would still need a similar CI workflow, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to distinguish "v1" tag from version tags (like v1.20.0) here to make sure that we don't trigger a release when we push "v1" tag to its new position. I changed it to "v*.*", wdyt ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh right, good catch! "v*.*" sounds good. Can you add a comment about this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes ! 😄
e49a78d
to
c3e0aeb
Compare
c3e0aeb
to
c9712e0
Compare
This MR aims to prepare this project for semi-pinned tags for major versions.
Tags will be created and updated in ggshield-tools release script.
This MR needs to be merged first.
Works with MR#22 on ggshield-tools. Needs to be merged first.