feat: fix CI release branch #4
Merged
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
github-actions bot
pushed a commit
that referenced
this pull request
May 9, 2025
# [1.6.0](v1.5.0...v1.6.0) (2025-05-09) ### Features * fix CI release branch ([#4](#4)) ([cfdd37d](cfdd37d))
Contributor
Author
|
it seems that if you removed the tag 'v1.6.0' The workflow would work https://github.com/officialpycasbin/redis-watcher/actions/runs/14927411499/job/41935344480 Btw, this PR with the new |
hsluoyz
pushed a commit
that referenced
this pull request
May 9, 2025
github-actions bot
pushed a commit
that referenced
this pull request
May 9, 2025
# [1.6.0](v1.5.0...v1.6.0) (2025-05-09) ### Features * fix CI release branch ([#4](#4)) ([a9b86f1](a9b86f1))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I was not able to test this, but I checked the semantic-release-pypi changes between 3.0.0 and the latest version and it seems that this still works with node >=18. So bumping this should still work as expected.