Repository navigation
Release the SDK through changesets as 0.1.0 - #1289
Conversation
Set the SDK to 0.0.0 with a minor changeset so the version PR lists it, writes its CHANGELOG, and publishes 0.1.0. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011zYKsSCeiPusqfzgGJSZeq
🦋 Changeset detectedLatest commit: 25d7bee The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one): 2
🚫 Excluded labels (none allowed): 1
Please check the settings in the CodeRabbit UI or the
 |
The version PR (#1282) doesn't mention
@buildinternet/uploads-sdkbecause no changeset names it.changeset publishwould probably still publish 0.1.0 because that version isn't on npm, but nothing in the version PR shows that will happen.This PR makes the release explicit:
0.0.0.minorchangeset is added for it.Once this merges, #1282 lists @buildinternet/uploads-sdk@0.1.0, writes
packages/sdk/CHANGELOG.md, and publishes the SDK throughrelease.ymlalongside CLI 0.60.1. That first publish also validates the npm trusted publisher, which has to be used before Oct 26, 19:18 UTC.Checked locally:
changeset-lintpasses,changeset statuslists the SDK at minor, and a throwawaychangeset versionrun produced0.1.0with the CHANGELOG entry.Generated by Claude Code