[DOCS] Mention package renaming and 5.x upgrade hurdles #460
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
The extension settings need to move as well after the package was renamed.
Add a note about the package renaming into the changelogs. Refs web-vision#452
pixelbrackets
force-pushed
the
add-renaming-note
branch
from
eaf356b to
6d33490
Compare
sbuerk
changed the title
sbuerk
approved these changes
May 7, 2025
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.
Update to 5.0 was possible, but then I had to migrate the extension settings,
which showed that the package key was changed as well.
I added a note about this into the Changelog, since this is a rather large alteration.