Repository navigation
chore(sdk): release nirium 0.16.1 - #116
Merged
Merged
Conversation
Bump to 0.16.1 and move the Unreleased changelog entries under it. README and package.json metadata only; dist/ is identical to the published 0.16.0 (compared file by file against the npm tarball). nirium-mcp is not part of this release. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release PR for
nirium0.16.1. Documentation and package metadata only. Nothing is published or tagged by this PR.packages/sdk/package.jsonandpackage-lock.json: 0.16.0 to 0.16.1.packages/sdk/CHANGELOG.md: the Unreleased entries (from docs(sdk): document the x402Serve() guard, fix links and repository fields #115) moved under0.16.1 - 2026-10-11.Compared with the published tarballs from npm (not with a local copy): I built
dist/from this commit and randiff -ragainstnirium@0.16.0from the registry. All 20 files indist/are identical. Thepackage.jsondiffers only inversion,repositoryandbugs. Thenpm pack --dry-runfile list matches the 0.16.0 tarball (22 files).nirium-mcpis not in this release. It does not depend onnirium(no such entry in its dependencies), and itsdist/also builds identical to the published 0.6.0 (1 file). But it hardcodes its version insrc/index.ts(serverversion: '0.6.0'and a log line), so a metadata-only 0.6.1 would announce 0.6.0 at runtime. That needs a decision before it ships.🤖 Generated with Claude Code