Namegarage

Packaging patch: SDK 0.3.2 and catalog skill 1.3.2

Dev blog#api#release#architecture

Release 2026-11-17-installed-service-packaging changes packaging only. It aligns @namegarage/sdk 0.3.2, its two compatibility packages and the catalog skill 1.3.2 with the service that is already installed: API 1.3.0, MCP 1.3.1, UCP adapter 1.0.0 and A2A 1.0.0. Runtime behavior, methods, types, dependencies, routes, peers and quotas stay the same. The SDK and skill remain limited to public read-only catalog operations.

Why a patch

Release metadata belongs to the bytes you install. The published SDK 0.3.1 and skill 1.3.1 archives already bind their release ID to those component versions. This packaging patch gets its own ID and new immutable versions, leaving that earlier record intact. The new archives describe the installed service and use SDK 0.3.2 and skill 1.3.2.

What changed in the skill

Compared with published skill 1.3.1, the instructions differ only in two SDK pins, which move from 0.3.1 to 0.3.2. All other guidance is the same. The recorded skill_sha256 covers SKILL.md (67a5ea33dda4a45d9744eae3097562578c82398cf3ad96478092774de94129f5), not the companion release.json. Changing the release identity in release.json therefore does not change the hash of instructions that stayed the same.

Component versions in one record

The current release record and the developer changelog list every component version under one release ID. This ties the SDK, skill, API, MCP, UCP and A2A versions together without pretending that every component got a new version. Only the packages changed.

The earlier post Bitcoin without a processor still gives the background on the installed service, and this release does not change that service.

Before you install SDK 0.3.2 or skill v1.3.2, check the changelog for its current publication status.

Add as preferred source
Hacker News X LinkedIn Email

Using this button loads Google’s service and allows its usage measurement. Privacy policy.

Get new blog posts by email

Comments

Comments are reviewed before publication. The Author badge marks replies from the author.

Read approved comments on the discussion page.

    Open the discussion page

    Leave a comment

    Your account name, sign-in provider, and comment become public after review. Your email stays private. See the blog comments privacy notice and Privacy Policy.

    Sign in to leave a comment.