docs: add info box pointing to releases page for provider version#297
Open
sk31337 wants to merge 2 commits into
Open
docs: add info box pointing to releases page for provider version#297sk31337 wants to merge 2 commits into
sk31337 wants to merge 2 commits into
Conversation
dattito
approved these changes
May 28, 2026
Contributor
Author
|
@dattito please add approval/label/sacrifice for PR status check e2e test run to run :D |
Collaborator
|
I don't have permissions to start the tests. Other colleagues do. @SatabdiG can you trigger the tests? :) |
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
2 participants
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.
Summary
Adds a new
:::noteadmonition to the CloudFoundry provider configure guide (docs/end-user-guides/configure-provider-cf.mdx) telling readers where to find a valid value for<provider-version>in the manual install tab.The new box, in the same style as the existing notes:
Why
The YAML snippet uses
<provider-version>as a placeholder, but the docs didn't link to where supported versions are published. New users had to guess or search for the releases page.Test plan