Repository navigation
Conversation
Runs for a merged release PR get a read-only cache token, so the cache save is denied and the push job finds nothing. No frontend release since 26.4.1 has reached Docker Hub.
juho9000
force-pushed
the
fix/self-hosted-release-artifact-handover
branch
from
October 9, 2026 18:06
d317b02 to
fced0cd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gazebo's self-hosted release 26.7.6 was tagged but
codecov/self-hosted-frontendisstill at 26.4.1 (https://github.com/codecov/gazebo/actions/runs/28822509924). The
release workflow runs on
pull_request: closed, and since June GitHub issues aread-only cache token to runs for a merged PR, so the build job's cache save is denied
and
Push Self Hosted Release Imagefails on the miss. Same root cause and fix ascodecov/umbrella#2474.
The build job uploads the tarballs as a run-scoped artifact and the push jobs download
it. A second invocation in the same run (push rolling) reuses the uploaded image instead
of rebuilding; its download step in the first invocation reports an expected failure
(
continue-on-error).After merging, gazebo needs a new tag of this repo and a bump of its
@v1.2.14pinbefore the next frontend release.
Refs codecov/umbrella#2371, codecov/feedback#963