-
Notifications
You must be signed in to change notification settings - Fork 224
[BUG] "Token required because branch is protected" since 4/8 #1806
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
Labels
bug
Something isn't working
codecov/codecov-action
high
High Priority Issues (to be fixed within 2 sprints)
Comments
This was referenced Apr 14, 2025
@rix0rrr I pushed a fix for this in 5.4.1, can you see if that's working for you? |
I think this fix just broke my build:
|
@HarelM sorry, |
Thanks for the quick turnaround @thomasrockhu-codecov! This seems to have solved the build failure I was facing. |
iankhou
added a commit
to cdklabs/cdk-from-cfn
that referenced
this issue
Apr 15, 2025
Resolution of codecov/codecov-action#1806 prevents codecov uploads from breaking now.
github-merge-queue bot
pushed a commit
to cdklabs/cdk-from-cfn
that referenced
this issue
Apr 16, 2025
Resolution of codecov/codecov-action#1806 prevents codecov uploads from breaking now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
codecov/codecov-action
high
High Priority Issues (to be fixed within 2 sprints)
Describe the bug
Since April 8, we are seeing the following behavior:
The day before, we saw the following behavior:
We haven't changed our workflow file in between those runs. It was:
One change that I could observe was that during the successful run it used CLI
10.3.0
and in the failed run it used CLI10.4.0
.We have since then downgraded to
10.3.0
, but that didn't make a difference, we are still seeing the same error with this:Both workflows are running on the main repo, neither was running on a fork. From these examples, one was running on
push: main
and one onpull_request
, but subsequent pushes tomain
are equally failing so that's not the root cause.The
Command is the same between the successful and failing run, but in the failing run it just doesn't seem to produce a value:
I am noticing that the URLs are different.
The text was updated successfully, but these errors were encountered: