Skip to content

fix: sync stale version strings to v6.0.0#1

Open
stevenobiajulu wants to merge 1 commit intogregmos:mainfrom
UseJunior:fix/sync-version-strings
Open

fix: sync stale version strings to v6.0.0#1
stevenobiajulu wants to merge 1 commit intogregmos:mainfrom
UseJunior:fix/sync-version-strings

Conversation

@stevenobiajulu
Copy link
Copy Markdown
Contributor

Found a few version references left over from the v5.x cycle while reading through the codebase. This syncs them all to match the v6.0.0 release:

  • server/pyproject.toml5.5.06.0.0
  • server/pii_shield_server.py — engine init log said v5.4.0v6.0.0
  • manifest.json — long description referenced v5.5v6.0.0
  • setup_pii_shield.bat — pointed users to pii-shield-v5.5.0.mcpbv6.0.0.mcpb
  • setup_pii_shield.sh — same as above

No functional changes — only string literals. The setup script fix is the most user-facing: anyone following the .bat/.sh post-install instructions would see a filename that doesn't exist in dist/.

pyproject.toml, engine init log, manifest.json long description,
and both setup scripts still referenced v5.4.0/v5.5.0 after the
v6.0.0 release. This syncs them all to match.
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.

1 participant