Package tt-vscode-toolkit as a pinned flake input #1

Merged

multica-agent merged 1 commit from vscode-toolkit-flake into master

2026-09-04 12:33:16 +02:00

multica-agent commented

2026-08-18 17:32:06 +02:00

Member

Adds tenstorrent/tt-vscode-toolkit as a pinned input and packages it in nix/tt-vscode-toolkit.nix: packages.tt-vscode-toolkit (declarative VS Code extension for vscode-with-extensions / programs.vscode.extensions) and packages.tt-vscode-toolkit-vsix (the .vsix). Built and layout-verified locally; also added to flake checks.

No fork was created: the repo rule keeps upstreams as pinned inputs with deltas in patches/, and the available Forgejo token cannot create repos anyway.

🤖 Generated with Claude Code

Adds tenstorrent/tt-vscode-toolkit as a pinned input and packages it in nix/tt-vscode-toolkit.nix: `packages.tt-vscode-toolkit` (declarative VS Code extension for vscode-with-extensions / programs.vscode.extensions) and `packages.tt-vscode-toolkit-vsix` (the .vsix). Built and layout-verified locally; also added to flake checks. No fork was created: the repo rule keeps upstreams as pinned inputs with deltas in patches/, and the available Forgejo token cannot create repos anyway. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

multica-agent added 1 commit

2026-08-18 17:32:06 +02:00

Package the TT VS Code toolkit from a pinned input instead of forking it

tt-stack-ci / Report upstream drift (pull_request) Successful in 4s

Details

tt-stack-ci / Build simulators and check the host module (pull_request) Failing after 30s

Details

5006d43448

The ask was a fork, but this repo's standing rule is that upstreams stay
pinned flake inputs with deltas in patches/ — forking is exactly the
failure mode the rule exists to prevent, and the Forgejo token cannot
create repos anyway. Pinning tt-vscode-toolkit at eba70fc and building
the .vsix with vsce inside buildNpmPackage gets the same outcome: every
NixOS machine can install the extension declaratively
(packages.tt-vscode-toolkit) or grab the .vsix (packages.tt-vscode-toolkit-vsix).

Non-obvious bits: upstream's npm run package wrapper needs .git for a
branch-dependent filename, so vsce is invoked directly; keytar (a vsce
dep) compiles against libsecret during npm ci; the lock file's
../tensix-viz entry is extraneous and ignored by npm ci.

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

Grok force-pushed vscode-toolkit-flake from 5006d43448

tt-stack-ci / Report upstream drift (pull_request) Successful in 4s

Details

tt-stack-ci / Build simulators and check the host module (pull_request) Failing after 30s

Details

to f45d370ff6

tt-stack-ci / Build simulators and check the host module (pull_request) Failing after 2s

Details

tt-stack-ci / Report upstream drift (pull_request) Successful in 5s

Details

2026-09-04 12:33:10 +02:00

Compare