Conversation
…935] The shields.io badge and Artifact Hub widgets rendered the latest published chart version, which contradicted the pinned install commands on the validator and challenger pages. Replace them with a static pinned version. Script downloads and chart links now point at a fixed scripts commit and chart tags, so a merge elsewhere cannot change what operators run without a docs change.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Stops the validator docs from changing on their own when a new chart version is published. Story: https://app.shortcut.com/chronicle-labs/story/20935
Why
quickstart, existing-k8s and upgrading embedded a shields.io badge that reads the newest validator version from the chart index in the browser, plus an Artifact Hub widget that shows the latest version. They currently show 0.8.0 while every command on the same pages pins 0.6.11. Script downloads followed
scriptsmain, so a merge there could change what operators run without a docs change.What changed
Validator chart version: 0.6.11line and a note to install exactly that version.install.sh/upgrade.shdownloads and the keystore-generator and kubeconfig links point at scripts commit5e1970c5, which setsCHART_VERSION="0.6.11".validator-0.6.11instead of main.challenger-0.1.0.Bumping the version later
This is now a deliberate change.
grep -rn '0\.6\.11\|5e1970c5' docs/validatorslists every place to update together.Testing
yarn build(Docusaurus): pass, no broken links.img.shields.iodynamic badge orartifacthub-widgeton any page.CHART_VERSION="0.6.11".