Repository navigation
chore: release v13.39.3 - #575
Merged
Merged
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
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.
Dates the CHANGELOG for v13.39.3. Laravel is still at 13.39 (the latest published is v13.39.0), so the framework goes up by a patch.
What it carries:
pollora/wp-rest2.0 is accepted (feat(deps): accept pollora/wp-rest 2.0 #571).composer updateinstalls it, and a REST route that declares no permission is then refused. The CHANGELOG says what to do first (Everyone::class, or thepollora/wp-rest/private_by_defaultfilter returningfalsewhile migrating, or"pollora/wp-rest": "^0.2"to stay).pollora/harness^0.1.15(chore: harness 0.1.15, and keep the development files out of the archive #570); this one had no CHANGELOG entry, it is written here.Tag and release only after the
developtomainpull request is merged, and with the owner's go-ahead.