3.0.2 #336
Merged
3.0.2 #336
Conversation
This file contains 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
Motivation: get folks to migrate after upgrading plugin
Motivation: users may just rush through the migration without reading carefully.
sherwinski
approved these changes
Dec 20, 2024
Update version numbers
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.
One line summary
Add an admin notice and updated styles to encourage settings migration.
Description
This update introduces an admin notice to prompt users to migrate their settings after upgrading the plugin. The notice is designed to be clear and prominent, ensuring that users are aware of the migration requirement.
V2 styles have been adjusted to emphasize the migration steps more effectively. These changes aim to reduce the likelihood of users skipping or misunderstanding critical instructions.
A missing
.gitignorefile has also been re-added.Screenshots
This change is