Version Packages - #3293
Open
squiggler-app[bot] wants to merge 1 commit into
Open
Conversation
squiggler-app
Bot
force-pushed
the
changeset-release/main
branch
7 times, most recently
from
August 17, 2026 12:19
b5ab181 to
d9f328d
Compare
squiggler-app
Bot
force-pushed
the
changeset-release/main
branch
from
August 17, 2026 12:20
d9f328d to
3fc8a55
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 main, this PR will be updated.
Releases
@sanity/parse-package-json@2.3.2
Patch Changes
32ecd1cThanks @rexxars! - Accept a runtime condition condensed to a plain string inpublishConfig.exports(
"node": "./dist/index.node.js"resolves identically to"node": {"default": "./dist/index.node.js"}), which is what is left of a{source, default}condition once
sourceis stripped for publishing. Validating an export subpath now also picks theexpected shape from the subpath itself, so a malformed entry is reported against the condition that
is wrong instead of as
A conditional CSS export must resolve to at least one ".css" file, and apackage.jsonvalidation error that carries its own message is printed as a message rather than asa raw issue object.
@sanity/pkg-utils@12.1.3
Patch Changes
#3290
32ecd1cThanks @rexxars! - Accept a runtime condition condensed to a plain string inpublishConfig.exports(
"node": "./dist/index.node.js"resolves identically to"node": {"default": "./dist/index.node.js"}), which is what is left of a{source, default}condition once
sourceis stripped for publishing. Validating an export subpath now also picks theexpected shape from the subpath itself, so a malformed entry is reported against the condition that
is wrong instead of as
A conditional CSS export must resolve to at least one ".css" file, and apackage.jsonvalidation error that carries its own message is printed as a message rather than asa raw issue object.
#3298
3aac365Thanks @squiggler-app! - fix(deps): update dependency tsx to ^4.23.12#3288
5bfa760Thanks @stipsan! - Stop flagging the synthesized namespace wrappers of the declaration bundler withae-missing-release-tag.Namespace re-exports (
export * as ns from './module', orimport * as ns+export {ns}) make the declaration bundling pass synthesize adeclare namespace <module>_d_exports {…}wrapper that drops the doc comment of the re-export statement, so the wrapper could never carry a release tag and there was no userland fix short of downgrading the rule for the whole package. The TSDoc check now recognizes those wrappers (the interop naming, declared as a namespace in the entry or a shared chunk, a body that only re-exports sibling declarations, and re-exported under an alias) and exempts them fromae-missing-release-tag, like API Extractor's own rollups never checked the equivalent namespace. Everything else, including user namespaces that merely resemble the interop naming, stays checked: a namespace that declares members of its own is yours to tag, even when the bundler's deconflicting hands it a wrapper-shaped name.Updated dependencies [
32ecd1c,5496b49,5bfa760]:@sanity/tsdown-config@0.24.2
Patch Changes
#3297
5496b49Thanks @squiggler-app! - fix(deps): update dependency rolldown to ~1.2.4#3288
5bfa760Thanks @stipsan! - Stop flagging the synthesized namespace wrappers of the declaration bundler withae-missing-release-tag.Namespace re-exports (
export * as ns from './module', orimport * as ns+export {ns}) make the declaration bundling pass synthesize adeclare namespace <module>_d_exports {…}wrapper that drops the doc comment of the re-export statement, so the wrapper could never carry a release tag and there was no userland fix short of downgrading the rule for the whole package. The TSDoc check now recognizes those wrappers (the interop naming, declared as a namespace in the entry or a shared chunk, a body that only re-exports sibling declarations, and re-exported under an alias) and exempts them fromae-missing-release-tag, like API Extractor's own rollups never checked the equivalent namespace. Everything else, including user namespaces that merely resemble the interop naming, stays checked: a namespace that declares members of its own is yours to tag, even when the bundler's deconflicting hands it a wrapper-shaped name.Updated dependencies [
5496b49]:@sanity/vanilla-extract-integration@0.1.13
Patch Changes
#3297
5496b49Thanks @squiggler-app! - fix(deps): update dependency rolldown to ~1.2.4#3299
45aa622Thanks @squiggler-app! - fix(deps): update dependency yuku-parser to ^0.8.7@sanity/vanilla-extract-rolldown-plugin@0.4.2
Patch Changes
#3297
5496b49Thanks @squiggler-app! - fix(deps): update dependency rolldown to ~1.2.4Updated dependencies [
5496b49,45aa622]:@sanity/vanilla-extract-tsdown-plugin@0.3.2
Patch Changes
#3297
5496b49Thanks @squiggler-app! - fix(deps): update dependency rolldown to ~1.2.4Updated dependencies [
5496b49]:@sanity/vanilla-extract-vite-plugin@0.2.13
Patch Changes
5496b49,45aa622]:Note
Low Risk
Release-only version and changelog updates; shipped behavior is patch-level validation, TSDoc, and dependency updates with no auth or data-path changes.
Overview
Automated Changesets release that bumps patch versions and changelogs across the monorepo; consumed changeset files are removed from
.changeset/.@sanity/parse-package-json@2.3.2 and @sanity/pkg-utils@12.1.3 ship fixes already merged on main:
publishConfig.exportsnow accepts runtime conditions condensed to a plain path string (e.g."node": "./dist/index.node.js"), export validation targets the subpath’s expected shape for clearer errors, and validation messages print as text instead of raw issue objects.@sanity/pkg-utils@12.1.3 and @sanity/tsdown-config@0.24.2 also stop reporting
ae-missing-release-tagon declaration-bundler–synthesized namespace wrappers fromexport * as nspatterns, while real user namespaces stay enforced.Remaining bumps are dependency patches (rolldown ~1.2.4, yuku-parser ^0.8.7, tsx ^4.23.12) propagated through the vanilla-extract and tsdown packages.
Reviewed by Cursor Bugbot for commit 3fc8a55. Bugbot is set up for automated code reviews on this repo. Configure here.