chore(master): release sdk-typescript 0.1.2 - #581
Conversation
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
Greptile SummaryThe PR prepares the TypeScript SDK 0.1.2 release.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| .release-please-manifest.json | Updates the TypeScript SDK release manifest from 0.1.1 to 0.1.2, consistent with the package metadata. |
| sdk/typescript/CHANGELOG.md | Adds the generated 0.1.2 release notes and the correct comparison range. |
| sdk/typescript/package-lock.json | Synchronizes both root package version fields to 0.1.2 without changing dependencies. |
| sdk/typescript/package.json | Bumps the published @arcbox/sandbox package version to 0.1.2. |
Reviews (4): Last reviewed commit: "chore(master): release sdk-typescript 0...." | Re-trigger Greptile
eb0b2d9 to
e84df68
Compare
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
e84df68 to
49e3857
Compare
|
Your Claude subscription has hit its usage limit. It resets at 12am (UTC). Re-trigger Pullfrog after the reset, or add an Add repo secret → · Model settings → · Setup docs → · Ask in Discord →
|
49e3857 to
5d1b7ce
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — the release-please bump cutting @arcbox/sandbox 0.1.2. No prior pullfrog review exists on this PR, so this pass covers the full 4-file diff rather than a delta; the branch was regenerated at 5d1b7ce to fold in the sdk/typescript commits that landed on master since the last regeneration.
- Bumped the version consistently across all three sites —
.release-please-manifest.json,package.json, and bothpackage-lock.jsonentries move0.1.1→0.1.2.sdk/typescript/srccarries no hardcoded version constant and the package declares noextra-files, so three sites is the complete set; root,fleet, andsdk/pythonmanifest entries are untouched. - Generated the 0.1.2 changelog section — 15 entries, none duplicated from the 0.1.1 section, and the newest
sdk/typescript-touching commit onmaster(a54746e) is captured. The three commits that landed after it (8bbe9b8,7c7861b,6ad91a8) touch only the Python SDK and are correctly absent. - Confirmed the patch bump is the configured behavior, not an under-bump — despite seven
featentries,release-please-config.jsonsetsbump-patch-for-minor-pre-major: true, so pre-1.0 features bump the patch. This matches how 0.1.1 was cut. - Confirmed the publish path is wired and guarded — the
sdk-typescript-v0.1.2tag this merge mints matches thesdk-typescript-v*push trigger inrelease-sdk-typescript.yml, whoseVerify tag matches package.jsonstep passes against the bumpedpackage.json, with a registry-already-published idempotency skip ahead of the OIDC publish. - Confirmed
sdk/typescript/README.mdis not stale for this release — its Status table already documents the phase 2a/2b surface 0.1.2 ships (waitForLog,commands.list,filespath verbs,files.watch,ports.waitForPort), so the rendered npm package page will be accurate on publish.
Claude Opus | 𝕏

🤖 I have created a release beep boop
0.1.2 (2026-08-10)
Features
Bug Fixes
Tests
Documentation
Continuous Integration
This PR was generated with Release Please. See documentation.