Skip to content
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

Revert "Bump codecov/codecov-action from 3 to 4 (#253)" #254

Merged
merged 1 commit into from
Sep 15, 2023
Merged

Revert "Bump codecov/codecov-action from 3 to 4 (#253)" #254

merged 1 commit into from
Sep 15, 2023

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Sep 15, 2023

This reverts commit 49a65ab.

The bump originated from an automated PR from Dependabot triggered by an accidental v4 tag push in the codecov/codecov-action repository: codecov/codecov-action#1089

The tag has since been removed due to the v4 major version series of the action still being in the beta development phase. That removal will cause subsequent runs of the workflow to fail:

Error: Unable to resolve action `codecov/codecov-action@v4`, unable to find version `v4`

So the action ref must be reverted back to v3. It can be bumped back to the v4 major version ref following the production 4.0.0 release in the action's repo.


Note: The Codecov upload token is no longer optional in v4 of the action:

https://github.com/107-systems/107-Arduino-Cyphal/actions/runs/6188762056/job/16801442689#step:4:17

Error: Codecov token not found. Please provide Codecov token with -t flag.

so it will be necessary to also adjust the workflow to provide the token to the action at the same time as the bump. Doing so is a good idea anyway because, although supported in v3, the lack of a token was causing periodic spurious coverage data upload failures. That was done already in the Arduino CLI repo (arduino/arduino-cli#2129) and the approach used there has passed the test of time with flying colors.

This reverts commit 49a65ab.

The bump originated from an automated PR from Dependabot triggered by an accidental v4 tag push in the
codecov/codecov-action repository.

The tag has since been removed due to the v4 major version series of the action still being in the beta development
phase. That removal caused subsequent runs of the workflow to fail:

Error: Unable to resolve action `codecov/codecov-action@v4`, unable to find version `v4`

So the action ref must be reverted back to v3. It can be bumped back to the v4 major version ref following the
production 4.0.0 release in the action's repo.
@per1234 per1234 added type: bug topic: ci Continuous integration for this repository. labels Sep 15, 2023
@codecov
Copy link

codecov bot commented Sep 15, 2023

Codecov Report

Patch has no changes to coverable lines.

📢 Thoughts on this report? Let us know!.

Copy link
Member

@aentinger aentinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the heads-up Per, I was suspecting just a spurious failure without looking deeper into it 👍

@aentinger aentinger merged commit 96a49a4 into 107-systems:main Sep 15, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: ci Continuous integration for this repository. type: bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants