Use non-permalink for HIGHEST_SUPPORTED_K8S_VERSION #424
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.
Reference Issues or PRs
Relates to nebari-dev/nebari#2301, nebari-dev/nebari#2276
What does this implement/fix?
The permalink to an old commit led me down a bit of a rabbit hole through the issues/PRs above to find out Nebari's plans for 1.26's planned EOL (e.g., references above). I think it would make more sense to use a non-permalink so readers are taken to the lastest commit and can see the current maximum supported k8s version. That said, I'm not sure whether the branch should be
develop
ormain
(this PR currently uses the default branch ofdevelop
).Put a
x
in the boxes that applyTesting
Documentation
Access-centered content checklist
Text styling
H1
or#
in markdown).Non-text content
Any other comments?