docs: Show edge rather than latest release #7717
Merged
Conversation
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
charlieegan3
force-pushed
the
docs-version-edge
branch
from
e49fbeb to
6daccb7
Compare
✅ Deploy Preview for openpolicyagent ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
johanfylling
approved these changes
Jun 23, 2025
| @@ -37,7 +34,7 @@ export default function CurrentVersionNavbarItem({ ...props }) { | |||
| <div className={styles.versionWrapper}> | |||
| <DefaultNavbarItem | |||
| {...props} | |||
| label={`${latestVersion}`} | |||
| label={"edge"} | |||
There was a problem hiding this comment.
Will this also affect the archived docs for specific OPA releases, or that's generated/created some other way?
There was a problem hiding this comment.
Yeah I kinda realised this was mostly not unhelpful unless we also had a way to set it. That will be used in the opa-docs repo, but this allows the site to be built with a version set.
There was a problem hiding this comment.
(So I have another commit to update this)
charlieegan3
force-pushed
the
docs-version-edge
branch
from
6daccb7 to
33b4ebe
Compare
added 2 commits
June 23, 2025 15:40
Docs are updated as we push to main, this means the version is not the latest, but rather the edge version. This is to avoid confusion while still showing fixes to the docs site as we make them, since it's still an active area of development after we released the new version. Signed-off-by: Charlie Egan <[email protected]>
This will be used to set the version in the navbar item on versioned deploys of the site. Signed-off-by: Charlie Egan <[email protected]>
charlieegan3
force-pushed
the
docs-version-edge
branch
from
33b4ebe to
220210c
Compare
✅ Deploy Preview for openpolicyagent ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Docs are updated as we push to main, this means the version is not the latest, but rather the edge version. This is to avoid confusion while still showing fixes to the docs site as we make them, since it's still an active area of development after we released the new version.
I have left in the component as we will want to make it so that this shows the latest tag when building an archived deployment and will use this component for that, but for now, it's just always shows edge.