We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have noticed that the outputs.version on the release-branch can be invalid.
outputs.version
Observed scenario:
0.0.1
main
codacy/[email protected]
Previous Version: 0.0.0
New Version: 0.0.1
Previous Version: 0.0.1
New Version: 0.0.2
After adding another tag 0.0.2 I got the output:
0.0.2
Previous Version: 0.0.2
New Version: 0.0.3
This cause me to assure, that at least two tags exists before being able to use the codacy/[email protected]
The text was updated successfully, but these errors were encountered:
Internal ticket created : TS-606
Sorry, something went wrong.
Folks I could find out, that the issue is related to the usage of s4u/[email protected]
s4u/[email protected]
Causes the issue:
- name: Prepare Maven uses: s4u/[email protected] with: java-version: ${{env.JAVA_VERSION}} - name: Check Version id: version uses: codacy/[email protected] with: release-branch: main
Does not cause the issue
- name: Check Version id: version uses: codacy/[email protected] with: release-branch: main - name: Prepare Maven uses: s4u/[email protected] with: java-version: ${{env.JAVA_VERSION}}
No branches or pull requests
I have noticed that the
outputs.version
on the release-branch can be invalid.Observed scenario:
0.0.1
and a release-branch namedmain
codacy/[email protected]
output onmain
:Previous Version: 0.0.0
New Version: 0.0.1
Previous Version: 0.0.1
New Version: 0.0.2
After adding another tag
0.0.2
I got the output:Previous Version: 0.0.2
New Version: 0.0.3
This cause me to assure, that at least two tags exists before being able to use the
codacy/[email protected]
The text was updated successfully, but these errors were encountered: