-
Notifications
You must be signed in to change notification settings - Fork 42
ci: publish major and minor tags #88
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
Merged
woile
merged 1 commit into
commitizen-tools:master
from
nikaro:ci/publish-major-minor-tag
Feb 5, 2025
Merged
ci: publish major and minor tags #88
woile
merged 1 commit into
commitizen-tools:master
from
nikaro:ci/publish-major-minor-tag
Feb 5, 2025
Conversation
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
Since you are using the default token with ${{ secrets.GITHUB_TOKEN }}
it may not be triggered automatically, though :-/
I added the workflow_dispatch
trigger to allow to run it manually on tags.
Please, update the bump version to use secrets.PERSONAL_ACCESS_TOKEN
, I've added the secret
Make sure major and minor tags are up to date on a patch release. This would allow the common practice to use major tag on the action: ```yaml - name: Create bump and changelog uses: commitizen-tools/commitizen-action@0 ``` (Ideally you may want to prefix version with `v` 🤷) This what this third party action does under the hood: ```bash $ TAG="0.21.0" $ MINOR="${TAG%.*}" $ echo $MINOR 0.21 $ MAJOR="${MINOR%.*}" $ echo $MAJOR 0 ``` This is used here for example: https://github.com/astral-sh/setup-uv/blob/main/.github/workflows/update-major-minor-tags.yml
@nikaro
nikaro
force-pushed
the
ci/publish-major-minor-tag
branch
from
February 5, 2025 09:02
0ce327f
to
0121edc
Compare
Please, update the bump version to use
secrets.PERSONAL_ACCESS_TOKEN
, I've added the secret
Hi, i've done it.
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.
Make sure major and minor tags are up to date on a patch release.
This would allow the common practice to use major tag on the action:
(Ideally you may want to prefix version with
v
🤷)This what this third party action does under the hood:
This is used here for example: https://github.com/astral-sh/setup-uv/blob/main/.github/workflows/update-major-minor-tags.yml