borgmcp-server 3.4.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-server/v/3.4.0
• Live integrity: sha512-ygun4Pt/LrShu9F/cRDw7LmQNnYUV0Cp7AbGjtIQfp2tluBxw5wADD6P4hAseVUGRX33jCoJk7a+3W6+GddsVg==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-server/releases/tag/v3.4.0
• Commit: 9606cce

News and fixes

borgmcp-server 3.4.0

• The server now uses borgmcp-shared 1.2.0 while protocol tag 13 remains unchanged. This release adds input refusals without changing protocol shapes.
• Migration 29 makes cube names unique per owner and role names unique per cube using ASCII case-insensitive comparison. Existing spelling and capitalization remain unchanged. A database containing names that differ only by ASCII letter case refuses to migrate, and the failed migration leaves its schema and rows unchanged.
• Creating a same-owner cube or same-cube role whose name differs from an existing name only by ASCII letter case now returns HTTP 409. Different owners may continue to use the same cube name, and a role may be renamed by changing only its capitalization.
• Role names must contain 1 to 64 bytes, start with an ASCII letter or number, and otherwise use only ASCII letters, numbers, spaces, periods, underscores, or hyphens.
• Repository association conformance now accepts a second repository association to the same cube and verifies that both associations remain observable.
• After borgmcp 4.9.0 is published, install borgmcp-server 3.4.0 and restart the live server. Migration 29 applies during that restart; report a collision refusal to the operator and never bypass it.