[tis24dev]

Automated release PR for v0.1.1-beta.

Greptile Summary

This PR prepares the v0.1.1-beta release. The main changes are:

• Package versions bumped to 0.1.1-beta.
• Project license changed to PolyForm Noncommercial.
• SPDX headers added across source, config, test, and script files.
• A GitHub Actions header check added for tracked source-like files.

Confidence Score: 4/5

The release install path can break because the workspace manifests and lockfile metadata are out of sync.

• Header placement looks valid for the changed TS, JS, shell, config, and HTML files.
• The new header workflow matches the current tracked files and keeps the vendored QR code exception.
• The changed package metadata needs a matching lockfile update before the release workflow can rely on npm ci.

package-lock.json

Important Files Changed

Filename	Overview
.github/workflows/license-header.yml	Adds a CI check for PolyForm SPDX headers with one documented third-party exception.
shared/package.json	Updates the publishable protocol package version and license, but the lockfile metadata remains stale.
clients/tabby/package.json	Updates the publishable Tabby plugin version and license while leaving discovery metadata unchanged.

_{Reviews (1): Last reviewed commit: "chore: set version 0.1.1-beta" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[sourcery-ai]

Sorry @tis24dev, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

@tis24dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 46cda936-940a-4312-a5e7-ce05cf11a9c2

📥 Commits

Reviewing files that changed from the base of the PR and between ef441e1 and b3977ec.

📒 Files selected for processing (58)

• .eslintrc.cjs
• .github/scripts/release-policy.sh
• .github/workflows/license-header.yml
• LICENSE
• NOTICE
• README.md
• clients/tabby/package.json
• clients/tabby/src/account/account.service.ts
• clients/tabby/src/account/login-modal.component.ts
• clients/tabby/src/config.ts
• clients/tabby/src/guest/mirrorSession.ts
• clients/tabby/src/guest/mirrorTab.component.ts
• clients/tabby/src/host/share-info-modal.component.ts
• clients/tabby/src/host/shareController.ts
• clients/tabby/src/index.ts
• clients/tabby/src/providers/tabContextMenu.ts
• clients/tabby/src/providers/toolbarButtonProvider.ts
• clients/tabby/src/services/peershell.service.ts
• clients/tabby/src/settings/settings-tab.component.ts
• clients/tabby/src/settings/settings-tab.provider.ts
• clients/tabby/src/types/tabby.d.ts
• clients/tabby/test/hostGuest.integration.test.ts
• clients/tabby/test/shareController.test.ts
• clients/tabby/test/smoke-load.cjs
• clients/tabby/webpack.config.mjs
• clients/web/package.json
• clients/web/src/index.html
• clients/web/src/index.ts
• clients/web/webpack.config.mjs
• jest.config.cjs
• jest.setup.cjs
• package.json
• scripts/check-version-lockstep.mjs
• scripts/copy-web-asset.mjs
• scripts/package-plugin.mjs
• scripts/publish-plugins.mjs
• server/package.json
• server/src/index.cjs
• shared/package.json
• shared/src/api.ts
• shared/src/base64.ts
• shared/src/httpTunnelHandler.ts
• shared/src/index.ts
• shared/src/mirrorController.ts
• shared/src/pinAuth.ts
• shared/src/protocol.ts
• shared/src/utf8Splitter.ts
• shared/src/websocketTransport.ts
• shared/test/auth.integration.test.ts
• shared/test/email.test.ts
• shared/test/httpTunnelHandler.test.ts
• shared/test/mirrorController.test.ts
• shared/test/pinAuth.test.ts
• shared/test/protocol.test.ts
• shared/test/transport.integration.test.ts
• shared/test/tunnel.integration.test.ts
• shared/test/utf8Splitter.test.ts
• shared/test/websocketTransport.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

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.}

[greptile-apps]

Lockfile Metadata Stays Stale

When CI or the release workflow runs npm ci, the workspace manifests now say 0.1.1-beta with the PolyForm license while package-lock.json still records the old workspace versions and Apache license metadata. That leaves the release install using an out-of-sync lock snapshot, so the install/publish path can fail before the new packages are built.