Repository navigation
Bring the readme and package description up to date since v3.0.0 - #43
Merged
Merged
Conversation
- New Installation section: VIPM, LabVIEW 2020 or newer 64-bit, the palette and its Advanced sub-palette, where the examples go. - Name rules: how tool, prompt, input, output and argument names are converted, and when Add Tool / Add Prompt refuse with error 5010. - Protocol versions: older clients were described as "served exactly as before", but the fallback for an unknown version is now 2025-11-25 (was 2025-06-18). Say so. - Access control: "Since this version" named no version. It now says the default changed after v3.0.0. - The client config example is a real code fence instead of ''', the dangling "where:" is gone, and three typos are fixed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The package description in VIPM listed only tools, prompts, resources and pictures. It now also names elicitation, progress and cancellation, structured results and the local-only default with optional bearer token, and two typos are fixed. Library_Version still said 2.2.6.37, so a package built locally from main came out older than the released 3.0.0. It now says 3.0.0.0. The release workflow overwrites it from the tag, so released packages are unaffected. Release_Notes is left alone: the workflow writes it from the tag message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tests✅ All 64 tests passed. Per-test results
Protocol tests✅ Protocol tester output (0 failed required checks)VI diff reportNo VI, VIM or CTL files changed in this pull request. Report for commit ad1b9c0. The installable test package is under Artifacts of this run once the build job has finished. |
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
The readme and the VIPM package description had fallen behind the changes since v3.0.0. The readme now has an installation section, the name rules, the changed protocol fallback, and says which release changed the access-control default. The package description names the new features, and the
.vipbversion no longer lags behind the last release.Changes
readme.md(modified):a-z0-9_-, error 5010 for empty, longer than 64 characters or clashing names (from Make tool and prompt names valid MCP keys and refuse clashing names #21);''', the dangling "where:" is gone, typos fixed (purpouse ×2, ouputs, Resoruces).src/LabVIEW MCP Server SDK.vipb(modified):Description: typos fixed (Promps, informations) and one paragraph added on elicitation, progress and cancellation, structured results and access control;Library_Version2.2.6.37 → 3.0.0.0, so a local build is no longer older than the released 3.0.0. The release workflow still overwrites it from the tag.Release_Notesis left alone, the workflow writes it from the tag message.Verified
.vipbparses as XML, is still ASCII with CRLF throughout, and only the three lines above differ.Test-InstalledPackage.ps1(example install path).Not verified
.vipbwas not opened in VIPM and no package was built from this branch. The CI test build of this pull request covers that.#dependencies.Known rough edges
🤖 Generated with Claude Code