chore: bump SDK packages to 0.4.2#43
Merged
Merged
Conversation
Sync source versions with the next release tag so flowforge-sdk, flowforge-client, and flowforge-mcp-server all match what publish-sdks.yml will publish.
There was a problem hiding this comment.
Pull request overview
Aligns the source-of-truth package manifests for the Python SDK, TypeScript client, and MCP server with the intended v0.4.2 release tag (even though the publish workflow rewrites versions during publishing).
Changes:
- Bump
flowforge-sdk(Python) project version to0.4.2. - Bump
flowforge-client(TypeScript) package version to0.4.2. - Bump
flowforge-mcp-server(npm) package version to0.4.2.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| packages/flowforge-sdk/pyproject.toml | Updates Python SDK version metadata to 0.4.2. |
| packages/flowforge-mcp/package.json | Updates MCP server npm package version to 0.4.2. |
| packages/flowforge-client-ts/package.json | Updates TS client npm package version to 0.4.2. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| [project] | ||
| name = "flowforge-sdk" | ||
| version = "0.2.11" | ||
| version = "0.4.2" |
| { | ||
| "name": "flowforge-mcp-server", | ||
| "version": "0.2.0", | ||
| "version": "0.4.2", |
| { | ||
| "name": "flowforge-mcp-server", | ||
| "version": "0.2.0", | ||
| "version": "0.4.2", |
| { | ||
| "name": "flowforge-mcp-server", | ||
| "version": "0.2.0", | ||
| "version": "0.4.2", |
- flowforge-sdk: bump __version__ in flowforge/__init__.py - flowforge-mcp: update hardcoded "0.2.0" in McpServer constructor, CLI usage banner, and /health response to "0.4.2" - flowforge-mcp: bump flowforge-client dependency from ^0.1.0 to ^0.4.0 (range covers currently-published 0.4.1 and the upcoming 0.4.2 release) - flowforge-mcp: regenerate package-lock.json so npm ci in CI doesn't fail on the version mismatch
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
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.
Summary
packages/flowforge-sdk/pyproject.toml0.2.11 → 0.4.2packages/flowforge-client-ts/package.json0.1.0 → 0.4.2packages/flowforge-mcp/package.json0.2.0 → 0.4.2Aligns source versions with the next release tag (latest released: v0.4.1).
publish-sdks.ymlrewrites these on publish anyway, but keeping source in sync makes the diff trail honest.Test plan
v0.4.2to triggerpublish-sdks.yml