Comments (3)
Hey @anton-yurchenko,
thanks for reaching out!
The
latest
tag was present without a release during a CI execution. You should be able to switch to the initial configuration with possible manual cleanup of tag and/or release.
I read the log as well and thought the same. That's why that particular code change was not obvious to work around that.
I tried deleting the release and tag manually via Github UI before running the action. Before creating this issue but also now.
These are my findings:
working workflow configuration from above:
- delete release and tag via Github UI
- let a commit with commitmessage "message 1" trigger the action
- release and tag are created with the text "message 1"
- let a commit with commitmessage "message 2" trigger the action
- release and tag are updated with the text "message 2"
non-working workflow configuration from above:
- delete release and tag via Github UI
- let a commit with commitmessage "message 1" trigger the action
- release and tag are created with the text "message 1"
- let a commit with commitmessage "message 2" trigger the action
- release and tag are NOT updated and text of both stay are still "message 1"
Does that come in hand with your answer?
As I have no other action creating the tag I think the Github API call of your action creates both the release and the tag. With the additional DRAFT_RELEASE
passed to the Gibhub API, Github might not be able to update the release because it strugles with the tag.
The Github API creates both in the first run but then has struggle with the already existing tag in the second run as it seams?!
I understood the action as to update the latest
release also if it already exists.
Is this valid or is this something false in the back of my mind?
Why I want to use this: I want to use it for a release-branch which should create a release with artifacts each time a commit is pushed to that branch.
from git-release.
Hello @treee111, thanks for raising this issue.
According to the log from the failed execution, it seems that the execution crashed while trying to create an already existing latest
tag:
WARNING precedent release not found
FATAL error creating latest tag: POST https://api.github.com/repos/treee111/wahooMapsCreator/git/refs: 422 Reference already exists []
Currently, git-release does not validate the latest
tag existence and assumes it is absent when no release is found.
The PR fix must be a coincidence because DRAFT_RELEASE
is not used within the action itself but passed as is to the GitHub API during a release creation call.
The latest
tag was present without a release during a CI execution. You should be able to switch to the initial configuration with possible manual cleanup of tag and/or release.
P.S: I wil look into improving that in future releases
from git-release.
Hello @treee111,
This behavior was improved in v5.0.2.
Please reopen this issue or leave a comment if the problem persists.
P.S: I noticed you use the latest
version in your flow. It is recommended to lock to a major version instead, like v5
, and update using dependabot or equivalent
from git-release.
Related Issues (20)
- error reading changelog: changelog file does not contain version HOT 1
- FATAL error reading changelog: changelog file does not contain version 1.1.2 HOT 6
- PRE_RELEASE/UNRELEASED always creates a new DRAFT release HOT 5
- Empty tag prefix HOT 3
- Allow taking the latest changelog version instead of using TAG_PREFIX_REGEX HOT 3
- Support a "Unreleased" pre-release HOT 3
- Development tags are not matched correctly HOT 1
- [QUESTION] How to do prerelease like on suffix? HOT 2
- How to restict folders and files for the Release? HOT 3
- CHANGELOG.md with empty Headings HOT 1
- Interpret CHANGELOG.md headlines with "v" HOT 1
- Support for GitLab? HOT 1
- Empty headlines in a release HOT 2
- Regression in v4.2+ HOT 8
- panic: runtime error: invalid memory address or nil pointer dereference HOT 6
- Upload error HOT 2
- Automate adding a footer to the release note HOT 1
- SIGSEGV on v5 when no changes for a version (Unreleased) HOT 1
- Isn't the default release name the tag?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from git-release.