Skip to content

fix(deps): update dependency @sanity/pkg-utils to v13 #2138

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.

Sign up for GitHub

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

Merged
squiggler-app merged 3 commits into from
Oct 9, 2026
Merged

fix(deps): update dependency @sanity/pkg-utils to v13 #2138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5199758
fix(deps): update dependency @sanity/pkg-utils to v13
squiggler-app[bot] Oct 9, 2026
dfda6b4
chore(deps): resolve @sanity/pkg-utils v13 with a single tsdown 0.23 …
cursoragent Oct 9, 2026
f0596b9
docs(agents): note pnpm auto-added release-age excludes and knip hook…
cursoragent Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/dependencies-GH-2138.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@sanity/plugin-kit': patch
---

fix(deps): update dependency @sanity/pkg-utils to v13
4 changes: 4 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,8 @@ pnpm defaults `minimumReleaseAge` to 1 day (since v11). `minimumReleaseAgeExclud

Do **not** bypass the maturity check with `pnpm add … --config.minimumReleaseAge=0` (or any other `--config.minimumReleaseAge` override). That is not allowed. If `pnpm install` fails because a needed version is too new, add that exact `name@version` to `minimumReleaseAgeExclude` instead.

pnpm also writes such entries itself: when a package that `minimumReleaseAgeExclude` already lists (e.g. `yuku-parser`) resolves to a release that pins an exact, still-too-new version of a subdependency (e.g. `yuku-core@0.18.1` and its `@yuku-core/binding-*` platform packages), a lockfile-rewriting install appends those `name@version` entries to `pnpm-workspace.yaml`. Commit them (or a scoped glob such as `'@yuku-core/*'` for a family of platform binaries) with a short dated comment—`pnpm install --frozen-lockfile` in CI re-verifies the lockfile against `minimumReleaseAge` and fails with `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION` if the lockfile pins a too-new version that is not excluded. `minimumReleaseAgeExcludePrune` removes the exact entries once they age out.

## Before Submitting a PR

Run these commands in order. **All must pass** or CI will fail:
Expand Down Expand Up @@ -673,6 +675,8 @@ Tests run against the dedicated bare-bones `dev/e2e-studio` (workspaces `/chromi

Standard commands from the Quick Reference table apply. Run `pnpm build` before `pnpm lint` if type errors reference missing `dist/` output. `pretest` automatically builds all packages except `dev/*` before Vitest runs.

`pnpm knip` reports `lefthook` as an unused devDependency on these VMs because knip's lefthook plugin follows `git config core.hooksPath`, which Cursor Cloud points at its own agent hooks directory instead of `.git/hooks`. CI is unaffected. To reproduce the CI result locally, override the setting for that one process: `GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=core.hooksPath GIT_CONFIG_VALUE_0=.git/hooks pnpm knip`.

## Related Documentation

- [CONTRIBUTING.md](./CONTRIBUTING.md) - Human contributor guide
Expand Down
Loading
Loading