chore(deps): update dependency @scalar/api-reference to v1.64.1 - #795
Open
github-actions[bot] wants to merge 1 commit into
Open
chore(deps): update dependency @scalar/api-reference to v1.64.1#795github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Closed
github-actions
Bot
force-pushed
the
renovate/scalar-api-reference-updates
branch
from
July 20, 2026 21:25
c3afc6e to
d09f123
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
renovate/scalar-api-reference-updates
branch
from
July 31, 2026 01:34
d09f123 to
3f06b6b
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
renovate/scalar-api-reference-updates
branch
from
August 3, 2026 09:10
3f06b6b to
fb222a9
Compare
bussyjd
added a commit
that referenced
this pull request
Aug 5, 2026
Applied directly rather than merging the PR branches: all four are cut from main while this branch carries newer intermediate versions from rc1's own renovate merges, so every one of them conflicts on every file it touches. Hand-resolving those conflicts is how a dependency silently gets downgraded, so the target versions are applied in one commit instead — the same shape renovate would emit if it rebased onto rc2. obolup.sh (#797): - kubectl 1.36.2 -> 1.36.3, helmfile 1.7.1 -> 1.7.2, helm-diff 3.15.10 -> 3.15.11, ollama 0.32.1 -> 0.32.5 ethereum clients (#796): - geth v1.17.4 -> v1.17.5, nethermind 1.39.1 -> 1.39.2, besu 26.7.0 -> 26.7.1, erigon v3.5.2 -> v3.5.4, lighthouse v8.2.0 -> v8.2.1, prysm v7.1.7 -> v7.1.8, lodestar v1.44.0 -> v1.45.0 (reth and teku were already at target; nimbus tracks a different renovate datasource and had no PR, so it is left alone) scalar (#795): - @scalar/api-reference 1.62.9 -> 1.64.0 with its matching SRI hash, which must move in lockstep or the browser blocks the script cloudflared (#794): - 2026.7.2 -> 2026.7.3 with its matching image digest
github-actions
Bot
force-pushed
the
renovate/scalar-api-reference-updates
branch
from
August 7, 2026 14:22
fb222a9 to
c330af8
Compare
github-actions
Bot
changed the title
bussyjd
approved these changes
Aug 8, 2026
github-actions
Bot
force-pushed
the
renovate/scalar-api-reference-updates
branch
from
August 8, 2026 15:07
c330af8 to
e111858
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
1 participant
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.
This PR updates the @scalar/api-reference bundle pinned in
internal/serviceoffercontroller/scalar_html.go(the /api docs UI served over the public tunnel).SRI hash
scripts/update-scalar-sri.shran as a post-upgrade task and refreshedscalarBundleSRIin the same commit. Verify the diff touches BOTH const lines — if only the version moved, the task was blocked; run the script on this branch before merging or the browser blocks the bundle and /api renders blank.What Changed
Auto-generated by Renovate Bot