Open
Conversation
github-actions
bot
force-pushed
the
changeset-release/develop
branch
from
63f6db9 to
1e914f0
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
bot
force-pushed
the
changeset-release/develop
branch
from
1e914f0 to
96d08a0
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to develop, this PR will be updated.
developis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitondevelop.Releases
@headstartwp/block-primitives@0.1.1-next.0
Patch Changes
@headstartwp/core@1.6.1-next.0
Patch Changes
shouldSkipRedirectincorrectly skips cross-domain redirects when pathnames match #941@headstartwp/next@1.5.3-next.0
Patch Changes
@headstartwp/headstartwp@1.3.2-next.0
Patch Changes
Note
Low Risk
Primarily a prerelease/version roll-up plus dependency bumps; the only direct runtime change in this PR is the WP plugin version constant update.
Overview
Enters/updates Changesets pre-release mode for the
nexttag (.changeset/pre.json) and publishes a new prerelease set.Bumps versions and dependency ranges for
@headstartwp/core(1.6.1-next.0),@headstartwp/next(1.5.3-next.0),@headstartwp/block-primitives(0.1.1-next.0), and the@headstartwp/headstartwpWP plugin (1.3.2-next.0), cascading those prerelease deps through example/test projects.Changelogs document two patch fixes being released:
shouldSkipRedirectno longer skips cross-domain redirects when pathnames match, andextend_post_contentavoids a PHP 8+ “Undefined array key” warning via a null-coalescing check;plugin.phpis updated to the new plugin version constant.Written by Cursor Bugbot for commit 96d08a0. This will update automatically on new commits. Configure here.