Skip to content

chore(sdk): release 0.4.0 — republish expanded client surface; pin CLI/MCP deps#342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dodeja merged 1 commit into from
Aug 22, 2026
Merged

chore(sdk): release 0.4.0 — republish expanded client surface; pin CLI/MCP deps #342

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .release-please-manifest.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
{
"sdks/typescript-sdk": "0.3.1",
"sdks/typescript-sdk": "0.4.0",
"sdks/typescript-sdk-cli": "0.1.0"
}
6 changes: 3 additions & 3 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/mcp/package.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -31,7 +31,7 @@
"@modelcontextprotocol/server": "^2.0.0",
"@posthog/mcp": "^0.11.7",
"@sentry/node": "^10.55.0",
"@terminal49/sdk": "0.3.1",
"@terminal49/sdk": "0.4.0",

@vorfluxvorfluxBotAug 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This updates the MCP manifest to SDK 0.4.0, but the documented npm run sdk:setup path still hard-codes const sdkSemver = '0.2.0' in packages/mcp/scripts/sdk-setup.mjs. Running it with its default published mode—or the documented T49_SDK_SOURCE=published—therefore installs @terminal49/sdk@0.2.0 with --no-save, overriding the version declared here and defeating this pin. Update the helper to install 0.4.0, preferably by reading dependencies['@terminal49/sdk'] from this package manifest so future releases cannot drift again.

"posthog-node": "^5.0.0",
"zod": "~4.3.6"
},
Expand Down
2 changes: 1 addition & 1 deletion sdks/typescript-sdk-cli/package.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -54,7 +54,7 @@
"prepublishOnly": "npm run build && npm run lint && npm run test"
},
"dependencies": {
"@terminal49/sdk": "0.3.1",
"@terminal49/sdk": "0.4.0",

@vorfluxvorfluxBotAug 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pinning the CLI to SDK 0.4.0 does not currently result in an installable CLI release. @terminal49/cli has no package entry on npm, while .github/workflows/publish_typescript_cli.yml relies exclusively on OIDC trusted publishing. npm requires the package to exist before a trusted publisher can be configured, so the first publication needs an approved bootstrap publication before this workflow can work. This is not theoretical: the cli-v-v0.1.0 release built and tested successfully after this change, then failed specifically at the npm publish step, and npm view @terminal49/cli still returns 404. Bootstrap the package, configure .github/workflows/publish_typescript_cli.yml as its trusted publisher, and then retry the release; otherwise the stated npm install -g @terminal49/cli outcome remains unavailable.

"cli-table3": "^0.6.5",
"commander": "^13.0.0"
},
Expand Down
7 changes: 7 additions & 0 deletions sdks/typescript-sdk/CHANGELOG.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -5,6 +5,13 @@ All notable changes to `@terminal49/sdk` are documented here.
Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [0.4.0](https://github.com/Terminal49/API/compare/sdk-v-v0.3.1...sdk-v-v0.4.0) (2026-08-22)


### Features

* **sdk:** publish the expanded client surface (terminals, vessels, webhooks, webhook notifications, mapTrackingRequest) that main has carried since 0.3.1, so the npm package matches the in-repo SDK the CLI and MCP server build against

## [0.3.1](https://github.com/Terminal49/API/compare/sdk-v-v0.3.0...sdk-v-v0.3.1) (2026-07-02)


Expand Down
2 changes: 1 addition & 1 deletion sdks/typescript-sdk/package.json
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
{
"name": "@terminal49/sdk",
"version": "0.3.1",
"version": "0.4.0",

@vorfluxvorfluxBotAug 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The SDK version is now 0.4.0, but sdks/typescript-sdk/package-lock.json still records 0.3.1 in both its top-level version and packages[""].version fields. That package-local lockfile is actively used by standalone SDK CI and by the publish workflow’s npm ci, and previous SDK releases updated it alongside package.json. Although npm currently tolerates a package-version-only mismatch during npm ci, this leaves committed release metadata inconsistent and causes the next lockfile regeneration to produce unrelated churn. Regenerate or update the package-local lockfile so both version fields are 0.4.0.

"description": "Terminal49 TypeScript SDK (JSON:API, openapi-fetch)",
"repository": {
"type": "git",
Expand Down
Loading