Document EP version picker fallback behavior#4185
Merged
Merged
Conversation
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| 1. **Pin override**: If the vendor has pinned this release to a specific branch, that branch's content is used. Pins always take priority. | ||
| 1. **Exact match**: If a branch exists with the same name as the selected version (e.g., branch `2.0.0` for version `2.0.0`), that branch's content is used. | ||
| 1. **Pin override**: If the vendor has pinned this release to a specific branch, that branch's content is used. Pins count as exact matches for version-picker filtering. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('is used').
| 1. **Pin override**: If the vendor has pinned this release to a specific branch, that branch's content is used. Pins always take priority. | ||
| 1. **Exact match**: If a branch exists with the same name as the selected version (e.g., branch `2.0.0` for version `2.0.0`), that branch's content is used. | ||
| 1. **Pin override**: If the vendor has pinned this release to a specific branch, that branch's content is used. Pins count as exact matches for version-picker filtering. | ||
| 1. **Exact or normalized match**: If a branch has the same name as the selected version, that branch's content is used. For example, branch `2.0.0` matches version `2.0.0`. Enterprise Portal also handles a `v` prefix mismatch. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.Passive] In general, use active voice instead of passive voice ('is used').
| To remove a version's dedicated content branch, delete the branch from your git repo. The branch disappears from the Content tab after the next sync. | ||
|
|
||
| However, if a release with that version label still exists on a customer's channel, the version still appears in the customer's version dropdown. The portal resolves it using the version resolution chain (nearest lower semver branch, then `main` as fallback). To fully remove a version from the customer's dropdown, the release must also be removed from the channel. | ||
| However, if a release with that version label still exists on a customer's channel, the version still appears in the customer's version dropdown by default. |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Replicated.SentenceLength] Try to keep your sentence length to 26 words or fewer.
AmberAlston
approved these changes
Jun 16, 2026
Member
|
@NoaheCampbell this is good to merge when you're ready |
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
3 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.
Documents the Enterprise Portal version picker behavior for releases that do not have matching content branches.
This adds guidance for the new Require matching content for release versions setting, including when vendors should leave fallback behavior enabled and when they should require explicit version-specific content.