Update/wp version checker#145
Merged
Merged
Conversation
iamdharmesh
approved these changes
Jun 29, 2023
iamdharmesh
left a comment
Member
There was a problem hiding this comment.
Thanks for updating this @jeffpaul.
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
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.
Description of the Change
This PR bumps the
skaut/wordpress-version-checkerdependency to 1.4.0 so that we can now get alerts when WordPress core hits Release Candidate for a major release if this plugin is not already set to be "tested up to" that new major version. This also adds an exception in the.gitattributesfile so that we don't distribute the new.wordpress-version-checker.jsonfile.How to test the Change
🤷🏼 YOLO merge?
Changelog Entry
Credits
Props @jeffpaul.
Checklist: