Skip to content

Refresh READMEs after the radius-sdk 0.1.0 / radius-cli 0.2.0 release - #38

Merged
azf20 merged 1 commit into
mainfrom
docs/post-release-refresh
Sep 24, 2026
Merged

azf20 merged 1 commit into
mainfrom
docs/post-release-refresh

Conversation

@azf20

@azf20 azf20 commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

READMEs still described the SDK as an unpublished PoC; npm shows that text on the radius-sdk package page.

  • packages/sdk/README.md: drop the PoC title, "not yet published" status and preview install notes; add an entry-point table (radius-sdk, /hono, /client and the peer each needs) and a pre-1.0 note linking the changelog; list every src/ module in the layout table.
  • packages/cli/README.md: SBC has a built-in default address (SBC.address from radius-sdk, same on mainnet and testnet); --sbc / RADIUS_SBC_ADDRESS only relocate it. The README said there was no default.
  • README.md: npm links, install lines, pointer to packages/sdk/examples; the CLI is bumped with every SDK release because of updateInternalDependencies: "patch", not 0.0.x pinning.
  • packages/sdk/examples/demo-dapp/README.md: run from the root with pnpm --filter radius-demo-dapp dev; the separate install step is gone now that examples are workspace packages.

Patch changesets for both packages so the npm READMEs refresh on the next release.

Docs only; changeset status lists both patch bumps.

🤖 Generated with Claude Code

…elease

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🦋 Changeset detected

Latest commit: fd86bf6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
radius-cli Patch
radius-sdk Patch

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

@azf20
azf20 merged commit a9a638e into main Sep 24, 2026
4 checks passed
@azf20
azf20 deleted the docs/post-release-refresh branch September 24, 2026 12:10
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.

2 participants