Skip to content

Changed source of the plugin to npm for auto-updates - #2564

Merged
paseo-bot[bot] merged 2 commits into
getpaseo:mainfrom
ActiveChooN:kanban-md-to-npm
Nov 17, 2026
Merged

paseo-bot[bot] merged 2 commits into
getpaseo:mainfrom
ActiveChooN:kanban-md-to-npm

Conversation

@ActiveChooN

Copy link
Copy Markdown
Contributor

No description provided.

@paseo-bot paseo-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kanban 0.2.0 from npm is approved and ready to publish, @ActiveChooN. Nothing is needed from you.

I checked the published tarball, which adds the header button and Paseo 0.16 support to the listed Git version. I found nothing to fix. The panel runs the kanban-md CLI without a shell and reads board files on the daemon machine. It makes no network requests, and the only runtime dependency is yaml.

Edit I made: I removed repository.commit from the record. The registry only accepts a repository commit on an npm listing when npm provenance backs it, and the package has none. The repository link stays, and the listing still installs exactly the reviewed tarball.

Your OVERVIEW.md, description and screenshots ship in the package, so the page needs no registry copy. This PR also replaces the Git update you requested in #2565, so I'm closing #2566 as a duplicate.

Review data
  • Artifact: npm @activechoon/kanban-md-paseo@0.2.0, tarball https://registry.npmjs.org/@activechoon/kanban-md-paseo/-/kanban-md-paseo-0.2.0.tgz. The SHA-512 of the downloaded tarball matches artifact.integrity and the integrity npm reports. The latest dist-tag is 0.2.0. The package repository tag v0.2.0 points at cb23950.
  • Compared with the listed Git commit 1b80b3b (0.1.0), using an extracted tarball against a git archive export with no submodules or hooks, and nothing was built or run. The only code change is the new client/header-buttons.ts: it registers an "Open Kanban" header button per workspace through the plugin client API. The server files are identical. Other changes are the ^0.16.0 range, @getpaseo/* 0.13.2 to 0.16.0 and ws 8.22.1 to 8.23.0 in the lockfile, and the version number.
  • Dependencies: npm-shrinkwrap.json pins every package to registry.npmjs.org with integrity. The only runtime dependency is yaml. The build is npm ci --omit=dev --ignore-scripts. The only install-script package is fsevents, a dev dependency that is omitted.
  • Execution and access: one execFile("kanban-md", …) with shell: false, a fixed argument list built from validated operations, a 10 s timeout and an output cap. The server reads the board config.yml and ticket files and writes tickets only through the CLI. There is no fetch, eval, environment read or generated code. The overview discloses the cross-project attachment search and that ticket content goes into prompts.
  • Registry edit: dropped repository.commit and refreshed reviewedAt. Trusted node scripts/validate.ts --online --changed --base origin/main: 555 well-formed and 1 matches its pinned artifact. The PR validate check passed on the reviewed head.
  • Not inspected: client rendering components line by line, and the plugin was not run.

@paseo-bot
paseo-bot Bot merged commit ef935f6 into getpaseo:main Nov 17, 2026
1 check passed
This was referenced Nov 17, 2026
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