-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/1.2.0 #111
Release/1.2.0 #111
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sidsector9 what was the PR/change that necessitated the WP/PHP minimum bumps here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated release date, so otherwise proceeding with the earlier release approval |
Oh for the love of all things automated and holy, now a failing E2E test on WP trunk. Looking at the string of commits, there's nothing from when that test was passing previously until now that should cause that failure here within the plugin repo. My gut is that something wonky is going on in WordPress 6.3 (in fact there's a bit of a hiccup in the Beta 1 release) so I'm choosing to chalk it up to oddities there that we'll catch & update when it gets to testing for WP 6.3 compatibility / "tested up to". |
Description of the Change
Release and version bump to 1.2.0.
Closes #110.
How to test the Change
Verify manually via VS Code or the GitHub UI.
Checklist: