Skip to content
Trazum

3.0.1

Released 2026-11-19

Added#

  • Trazum can be downloaded from the project's own places, with no marketplace account. (#774, #780, #781; advances #640, which stays open because no listing exists) The owner asked on 2026-11-19 for everything needed so it can be downloaded. Six parts:
    • Release files. A new assets job of release.yml, which needs the job that publishes (so after npm actually serves every package and after the release page exists; the publish order is untouched), builds trazum-vscode-<version>.vsix with @vscode/vsce@4.1.1 and trazum-mcp-<version>.mcpb with @anthropic-ai/mcpb@2.1.2 (mcpb validate first), makes SHA256SUMS over them and the bill of materials, and attaches the three with the workflow's own token. The job holds contents: write and no npm credential, id-token or environment, because it runs two packagers fetched by npx; the step that holds the token runs none of them. No marketplace, no new secret. The workflow makes no build-provenance attestation, so none is claimed. A manual run builds the files and attaches nothing. Built once here on 2026-11-19: the .vsix is 456,522 bytes in 132 files, the .mcpb 492,983 bytes in 132 files.
    • A fault the first .vsix had. npm run package:vscode produced 8 files and 8.39 kB, and none was @trazum/core, which dist/extension.js imports: the ignore file excluded node_modules. The extension would have failed to load for want of it. scripts/release-assets.mjs now lays the extension out with the closure the lockfile names and .vscodeignore lets exactly that package through. Not run inside VS Code or Cursor: only that the built dist/reading.js resolves its import from the unpacked file.
    • The bundle. manifest.json uses only fields of the format's MANIFEST.md (spec 0.3) and claims no platform: its compatibility is the Node version the package already declares. It holds the server's built files, @trazum/core's built files, the licence and the icon, and nothing the lockfile does not name. Its server was started from the unpacked bundle under plain Node and answered initialize and tools/list. Not opened in Claude Desktop. The bundle is unsigned.
    • The registry. The committed server.json stays npm only: the digest of a file built after the release PR merged cannot be in it. The mcp-registry job now waits for assets, downloads the bundle and SHA256SUMS from the release, and scripts/mcpb-registry-entry.mjs adds the mcpb entry (address and fileSha256) to the copy it publishes, refusing when the file and the sums disagree. A failed attachment therefore holds the listing back until the job is re-run. Not run: it runs for the first time at the next release.
    • Homebrew. packaging/homebrew/trazum.rb (@trazum/cli 3.0.0, its npm tarball's SHA-256, depends_on "node" and std_npm_args) is written by scripts/homebrew-formula.mjs, which compares the tarball's sha512 with the registry's before hashing it; a test holds the file to a fixture tarball with no network. Pushing it to the tap is a manual step, named in RELEASES.md: docs/compliance/secret-rotation.md covers no token for it and #781 forbids asking for one. Not tried with brew install.
    • Gemini CLI, Codex and the other clients. gemini-extension.json starts @trazum/mcp at the exact version with the skill as its context file (fields from Gemini CLI's own extension reference); docs/agents.md gains a table and snippets for Claude Code, Claude Desktop (bundle and JSON), Cursor, VS Code, Codex (command and TOML) and Gemini CLI, written by scripts/install-snippets.mjs from packages/mcp/package.json and held to it by a test. prepare-release.mjs moves the manifest and the table with the version. Not tried with gemini extensions install.
    • The page. /download, in the header, footer and sitemap and in the site's five languages: the CLI (npx, npm install -g, the tap) at the exact version, the MCP snippets drawn from the same source as docs/agents.md, the .vsix with how to install it, the Action's pinned line read from docs/setup.md, and the checksums. Links go to releases/download/v<version>/<name> for the version the site is built at, never releases/latest; so for a short while after a release merges, and for 2.7.12 itself, whose release carries none of these files, those addresses do not answer, and the page says so. It names no store, loads nothing and sends nothing: a twenty-fifth browser flow watches the network, measures contrast in both themes and checks a phone, and took 2,145 ms on 2026-11-19 against a local production build.