Skip to content

feat: add --manifest-version option to init command - #172

Merged
joan-anthropic merged 2 commits into
mainfrom
feat/init-manifest-version-option
Dec 4, 2025
Merged

feat: add --manifest-version option to init command#172
joan-anthropic merged 2 commits into
mainfrom
feat/init-manifest-version-option

Conversation

@joan-anthropic

@joan-anthropic joan-anthropic commented Dec 4, 2025

Copy link
Copy Markdown
Contributor

Summary

  • Add --manifest-version <version> option to the init command
  • Allow developers to specify which manifest version to use when creating a new manifest.json

Usage

mcpb init --manifest-version 0.3

Allow developers to specify which manifest version to use when
initializing a new manifest.json file.

Usage: mcpb init --manifest-version 0.3

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@asklar

asklar commented Dec 4, 2025

Copy link
Copy Markdown
Contributor

curious what is the scenario for choosing a "not latest"? is it so that it can work with clients that don't understand vLatest?

Break function parameters onto separate lines with trailing comma.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@joan-anthropic

Copy link
Copy Markdown
Contributor Author

curious what is the scenario for choosing a "not latest"? is it so that it can work with clients that don't understand vLatest?

Yep! Just that

@joan-anthropic
joan-anthropic merged commit 27083dc into main Dec 4, 2025
10 checks passed
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