-
Notifications
You must be signed in to change notification settings - Fork 8
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
Action fails due to argument passed to --drop-prefix #8
Comments
@choffmeister I get the same results when updating to v0.4.0 (via Dependabot PR). Is this unintentional, or should users of the action refrain from specifying explicit This is how I have the action configured in one of my projects for the v0.3.11 release: uses: choffmeister/[email protected]
with:
fallback: v0.0.0
drop-prefix: false
prerelease-prefix: dev
prerelease-suffix: ""
prerelease-timestamped: false Updating it to this configuration breaks CI: uses: choffmeister/[email protected]
with:
fallback: v0.0.0
drop-prefix: false
prerelease-prefix: dev
prerelease-suffix: ""
prerelease-timestamped: false with the same message that @sirajissani reported:
|
@sirajissani I have the version pinned to what I believe is v0.3.11 and it works (going from memory, responding quickly via mobile). Dependabot offered the latest version which failed to pass CI, so I did not accept the version bump. |
@atc0005 I just checked your recently run actions and they do fail exactly as mine even with |
@sirajissani Thanks for checking. I thought I remembered otherwise, but as you noted when I looked back at the earlier logs I see that you are correct. From your updated original post:
This appears to be the case. This is recorded in the logs for a recent CI job (https://github.com/atc0005/go-ci/actions/runs/7472502581/job/20334831671#step:7:8):
with the same result:
The @choffmeister would it be useful if we filed a separate GH issue for the Docker tags issue noted above? |
@sirajissani Potentially related: If understand the changes between v0.3.11 and v0.4.0 correctly, then the flag package was swapped out and the new one does not support explicitly setting a boolean flag as false. |
If you want to stick with v0.3.11, try this: - id: git_describe_semver
uses: choffmeister/[email protected] # version of the action
with:
fallback: 0.0.0
prerelease-prefix: pre
prerelease-suffix: ''
prerelease-timestamped: false
version: v0.3.11 # version of the tool |
The action fails with the following top level message on GitHub CI.
The issue is observed
0.3.11
as well as0.4.0
.However the issue is fixed on the main branch - that is
@main
worksGithub Action Logs
The workflow job is as follows
Could you please tag this release so that I could refer to it specifically. Also, it was a surprise that a later commit broke
0.3.11
. Perhaps the action always pulls thelatest
docker image. Any help for this would be greatly appreciated.The text was updated successfully, but these errors were encountered: