Version Packages (2026-01-rc) #3516
Closed
+1
−1
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
lrsterrett
force-pushed
the
changeset-release/2026-01-rc
branch
from
f84e7ad to
293de06
Compare
|
Hmm, without a changeset it won't trigger the npm release, right? This PR originally got triggered because because of a change meant for 2025-10, but that has since gotten merged |
I'm not sure honestly. Are we ready to release the 2026-01 rc? |
We had waited a couple of weeks to allow for bug fixes in 2025-10, but not sure if there's a good reason not to cut the release at this point 🤷 |
robin-drexler
approved these changes
Oct 22, 2025
|
After looking back at your work PRs to cut 2025-10-rc, I'm closing this mainly because of semantic consistency for branch names/PR titles. New PR |
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.
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 2026-01-rc, this PR will be updated.
Releases
@shopify/[email protected]
Patch Changes