Publish package to GitHub Packages

[dlddu]

What changed

• Rename the package to @buzzvil/redash-mcp and link it to this repository.
• Configure both the tagpr release path and manual tag release workflow to publish to https://npm.pkg.github.com with the repository GITHUB_TOKEN.
• Grant only the required packages: write permission and verify package contents before publishing.
• Document GitHub Packages authentication and npx @buzzvil/redash-mcp usage.

Why

The Buzzvil fork should be distributed from GitHub Packages under the Buzzvil scope and remain runnable through its existing npm bin entrypoint.

Impact

The next release tag will publish @buzzvil/redash-mcp to GitHub Packages without an NPM_TOKEN secret. Because the publishing workflow runs in this public repository, a newly created package inherits the repository visibility model. GitHub Packages still requires npm authentication for installs, even for public packages; the README now documents the required classic PAT with read:packages.

Validation

• npm ci
• npm run build
• npm test -- --runInBand (77 tests passed)
• npm pack --dry-run --json (dist/cli.js included and executable)
• node dist/cli.js --help
• Parsed both modified workflow files with js-yaml
• git diff --check

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f7b4bdb4-7f7c-4c7a-9f96-419a03c2a413

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}