[savvy-web-bot]

Dependency Updates

savvy-web-systems

Dependency	Type	Action	From	To
@okfit/plugin	devDependency	updated	^0.5.26	^0.5.27
@vitest-agent/plugin	devDependency	updated	^6.0.1	^6.0.2

@savvy-web/pnpm-plugin-silk

Dependency	Type	Action	From	To
rolldown-pnpm-config	devDependency	updated	^2.2.0	^2.2.1

@savvy-web/tsdown-plugins

Dependency	Type	Action	From	To
@tsdoctor/manifest	dependency	updated	^0.2.10	^0.2.11

@savvy-web/ai-plugins

Dependency	Type	Action	From	To
pluginfinity	devDependency	updated	^0.3.10	^0.3.11

Changesets

1 changeset(s) created for version management.

@savvy-web/tsdown-plugins

Changeset: savvy-web-tsdown-plugins-deps
Type: patch

## Dependencies

| Dependency | Type | Action | From | To |
| --- | --- | --- | --- | --- |
| @tsdoctor/manifest | dependency | updated | ^0.2.10 | ^0.2.11 |

---

This PR was automatically created by silk-update-action

chore(deps): update 1 dependency and 4 devDependencies

Signed-off-by: savvy-web-bot[bot] <229056750+savvy-web-bot[bot]@users.noreply.github.com>

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 5aebccb9-93bd-4620-9c8c-efaea4d0a63f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pullfrog]

✅ No new issues found. I'm not approving yet only because I couldn't read the CI check status in this run.

Reviewed changes

I reviewed the bot's re-pin of five dependency ranges against the lockfile and the changeset rules.

• Range-only re-pins: in all five importers: entries, only the specifier: line changes. The version: line below it is unchanged, so main already resolved each new floor: @okfit/plugin 0.5.27, @vitest-agent/plugin 6.0.2, rolldown-pnpm-config 2.2.1, @tsdoctor/manifest 0.2.11, pluginfinity 0.3.11. The lockfile has no other hunks, so no other package versions change.
• Changeset coverage is correct: @tsdoctor/manifest is a runtime dependency of @savvy-web/tsdown-plugins, so raising its published floor needs the patch changeset, and the PR includes it. rolldown-pnpm-config is a devDependency whose output ships inside pnpm-plugin-silk. It still resolves to 2.2.1 on both sides, so the published pnpmfile can't change and no changeset is needed. The root and plugin/ devDependency re-pins need no changeset either.
• pnpm-workspace.yaml key order: packages: moves from its alphabetical slot to the top of the file. The content is unchanged, so this has no effect on install. It is a recurring flip-flop: #840 moved it up, #841 put it back where PnpmWorkspace.sortContent places it (alphabetical, not moved to the top), and this PR moves it up again. The next commit through lint-staged will move it back. The step that moves it lives outside this repo, so nothing here needs to change.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}