Skip to content

Update release dependencies#2

Merged
austin-thesing merged 2 commits into
mainfrom
release/dependency-upgrades
Jun 16, 2026
Merged

Update release dependencies#2
austin-thesing merged 2 commits into
mainfrom
release/dependency-upgrades

Conversation

@austin-thesing

@austin-thesing austin-thesing commented Jun 16, 2026

Copy link
Copy Markdown
Member

Summary

  • Update root AI SDK/OpenTUI/Bun dependency ranges and lockfile.
  • Update website Astro/Starlight/Wrangler/browser tooling ranges and lockfile.
  • Externalize OpenTUI platform packages in the Bun build so native optional imports resolve at runtime.

Test plan

  • bun run typecheck
  • bun run build

Notes

  • npm audit still reports transitive Astro/Wrangler dev-server findings; npm's automated fix path downgrades Astro/Wrangler, so this PR leaves the latest versions in place.

Note

Update release dependencies and bump version to 0.2.22

  • Bumps version from 0.2.21 to 0.2.22 in package.json and updates description to mention AI gateway, Workers AI, and custom model support
  • Updates @ai-sdk/*, ai, @opentui/core, and related packages to newer releases with caret ranges; raises packageManager and engines.bun to 1.3.14
  • Adds --external "@opentui/core-*" to the build script so platform-specific @opentui/core packages are resolved at runtime instead of bundled
  • Updates website dependencies (@astrojs/starlight, astro, sharp, playwright, wrangler) in website/package.json
  • Behavioral Change: @opentui/core-* platform packages are no longer bundled, requiring them to be present in the install environment at runtime

Macroscope summarized aef1fdc.

Summary by CodeRabbit

  • Chores

    • Bumped package version to 0.2.22 and expanded the description to cover more AI integrations (including OpenRouter, AI gateways, Workers AI, and custom models).
    • Updated the required Bun toolchain to 1.3.14+.
    • Refreshed dependency versions across the package and website, using updated caret-based constraints.
  • Build/Packaging

    • Updated the build script to change how @opentui/core subpackages are bundled via an externalization flag.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Version bump from 0.2.21 to 0.2.22 in the main package.json, with an updated description, a new --external '@opentui/core-*' build flag, Bun toolchain upgraded to 1.3.14, and multiple AI SDK and @opentui/core dependencies refreshed to caret ranges. The website/package.json similarly bumps Astro, Sharp, Playwright, Puppeteer, and Wrangler to newer caret-range versions.

Changes

Dependency and Version Maintenance

Layer / File(s) Summary
Main package version, build script, and dependency updates
package.json
Version bumped to 0.2.22, description expanded to include AI gateways and Workers AI, --external '@opentui/core-*' added to the build script, Bun toolchain moved to >=1.3.14, and @ai-sdk/*, @opentui/core, and ai dependencies updated to caret ranges.
Website dependency version bumps
website/package.json
@astrojs/starlight, @fontsource/*, astro, and sharp in dependencies, plus playwright, puppeteer, and wrangler in devDependencies, all bumped to newer releases and switched from pinned to caret semver ranges.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update release dependencies' accurately describes the primary change, which is updating package dependencies across the project and website.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/dependency-upgrades

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 19: The build script uses single quotes around the '--external' flag
value '`@opentui/core-`*', which breaks on Windows npm script execution. Replace
the single quotes with double quotes around '`@opentui/core-`*' in the build
script to ensure cross-platform compatibility and proper quoting behavior across
all operating systems.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d45bca85-b162-43f2-9499-6b3c314c395e

📥 Commits

Reviewing files that changed from the base of the PR and between f45f9c8 and bc32198.

⛔ Files ignored due to path filters (2)
  • bun.lock is excluded by !**/*.lock
  • website/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • package.json
  • website/package.json

Comment thread package.json Outdated
Use cross-shell-safe quoting for the --external flag.

'@opentui/core-*' can break on Windows npm script execution because single quotes are passed literally. Use double quotes for portability.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: website/package-lock.jsonnpm/sharp@0.35.1npm/astro@6.4.7npm/wrangler@4.101.0npm/@emnapi/runtime@1.11.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @opentui/core is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/@opentui/core@0.4.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@opentui/core@0.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm astro is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: website/package-lock.jsonnpm/astro@6.4.7

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/astro@6.4.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: website/package-lock.jsonnpm/@astrojs/starlight@0.40.0npm/astro@6.4.7npm/js-yaml@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@austin-thesing
austin-thesing merged commit 09ed795 into main Jun 16, 2026
6 checks passed
@austin-thesing
austin-thesing deleted the release/dependency-upgrades branch June 23, 2026 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant