Security hardening: token validation, docs, release guide #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Security Hardening Implementation
Summary
Security-first hardening for Taskade MCP Server: token validation, HTTPS warning, and operational documentation.
Changes
QA Results (Local)
Deferred (Intentional)
.github/workflows/release.ymlusesyarn install.github/workflows/force-release.ymlusesyarn installpackageManagerfieldTesting
Files Changed
Note
Validates TASKADE_API_KEY and warns on HTTP/SSE, adds security/integration/release docs, and adopts pnpm workspace/tooling.
TASKADE_API_KEYinpackages/server/src/cli.ts(exit on missing/empty/short).access_tokeninpackages/server/src/http.ts.SECURITY.md,docs/CLAUDE_DESKTOP_CONFIG.md,docs/CURSOR_SSE_CONFIG.md, anddocs/RELEASING.md.README.mdwith Documentation and Security sections; add.env.exampleforTASKADE_API_KEY.packageManager, addpnpm-workspace.yaml, and update server build script to use pnpm.Written by Cursor Bugbot for commit 6b7b168. This will update automatically on new commits. Configure here.