changing name from v11 to eol as v12 is eol as well #6504
Closed
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
eshanrnh
reviewed
Oct 3, 2024
Contributor
eshanrnh
left a comment
eshanrnh
left a comment
There was a problem hiding this comment.
Thanks @alina-tincas for the PR 🙌 We will review as soon as we can.
Contributor
Author
|
closing this PR as the same changed are in this one: #6505 Forgot to switch back to master branch before creating new branch with the other changes, so all changes got into that PR 🙈 |
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.
Description
What did you add/update/change?
changing name from v11 to eol as v12 is now "legacy docs" as well
Type of suggestion
Product & version (if relevant)
cms v10, v13 and v14
Deadline (if relevant)
When should the content be published?
anytime