-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
v4: New major version tagged prematurely #1089
Comments
Sorry about this @3flex, this has been removed and replaced with |
This reverts commit c5b9662. Refs: codecov/codecov-action#1089
This reverts commit e8e71d2. See codecov/codecov-action#1089.
Was anyone able to make the v4 beta version to succeed uploading? I tried and it keeps failing to validate the token, even if I put put the token inside an environment, configured the pipeline to use that environment and passed it, see https://github.com/ansible/ansible-lint/pull/3764/files Still, pipelines fail complaining about missing token: https://github.com/ansible/ansible-lint/actions/runs/6313000590/job/17140193383 --- when clearly the token was passed.
|
This reverts commit 7f6eac9. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
This reverts commit 85284b2. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
This reverts commit 6f3f074. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
This reverts commit e9761c1. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
This reverts commit b7a9204. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
This reverts commit 24ce306. The tagging of codecov/codecov-action@v4 was premature: codecov/codecov-action#1089 Wait until v4 is out of beta to upgrade. Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
…to 3 codecov/codecov-action#1089 Signed-off-by: hagen1778 <roman@victoriametrics.com>
FYI, some might have already merged the v4 upgrade and will see errors now. Removing releases and tags from GitHub is probably not a good practice. I would suggest returning the v4 tag, but with v3 code and jumping a version number. I know it's annoying for you, but the damage is done, and that likely the best path of mitigation for paying customers. |
codecov v4 was reverted, this breaks the builds. See codecov/codecov-action#1089
@codingjoe I agree, also the setup doc is not up-to-date on the website and suggest using v4. |
I realise it's probably too late, but FYI using the
v4
tag while the new version is in beta causes tools like Renovate (and maybe dependabot?) to automatically open PRs to update to the new version, e.g. detekt/detekt#6490While it's in beta this is unexpected. The v4 tag should be deleted, and a
v4-beta
tag used instead.From https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management:
The text was updated successfully, but these errors were encountered: