docs: acknowledge API v2 in privacy claims; fix stale 57-tool references - #67
Merged
Conversation
|
Member
Author
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. 🤖 Generated with Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Docs-only accuracy sweep. Since the v2 tool layer shipped (
setupToolsV2inpackages/server/src/server.ts), the server calls bothhttps://www.taskade.com/api/v1andhttps://www.taskade.com/api/v2, and the total tool count is 62 (57 v1 + 5 v2). Four doc lines still claimed v1-only traffic or 57 tools.Changes
README.md(Privacy & Security)https://www.taskade.com/api/v1and does not send your data to other third-party services.https://www.taskade.com/api/v1andhttps://www.taskade.com/api/v2— and does not send your data to other third-party services.SECURITY.md(Privacy)https://www.taskade.com/api/v1) using the token you provide; …https://www.taskade.com/api/v1andhttps://www.taskade.com/api/v2) using the token you provide; …Dockerfile(LABEL description)examples/README.md(n8n)The only-Taskade guarantee is unchanged: v2 traffic also goes exclusively to
www.taskade.com— no data is sent to any other third-party service.Intentionally untouched: the two
CHANGELOG.mdentries saying "v1's 57 tools are unchanged" — those are historical release notes accurately describing the v1 layer's count when v2 shipped.Test plan
git grep -E '(talks|sends|requests) .*only .*api/v1'— the one remaining match (SECURITY.md:51) names both API bases on the same line; no claim omits v2.git grep -nE '57 (AI )?(Taskade )?tools|all 57' -- '*.md' Dockerfile— only the two historical CHANGELOG entries remain (accurate v1-layer counts, left as-is).yarn build(regen + bundle, tree stays clean),yarn lint,yarn test(17/17) all pass locally.Docs only — no runtime changes, no changeset.