Skip to content

fix(server): point fetch:openapi at the live v1 spec URL - #54

Merged
johnxie merged 1 commit into
mainfrom
fix/v1-spec-fetch-url
Jun 27, 2026
Merged

fix(server): point fetch:openapi at the live v1 spec URL#54
johnxie merged 1 commit into
mainfrom
fix/v1-spec-fetch-url

Conversation

@johnxie

@johnxie johnxie commented Jun 27, 2026

Copy link
Copy Markdown
Member

Why

yarn fetch:openapi curls https://www.taskade.com/api/documentation/yaml — which now 404s. The v1 spec moved to /api/documentation/v1/yaml (verified 200; v2 lives at /v2/yaml). Without this, the v1 spec can't be refreshed.

What

  • Update the URL to /api/documentation/v1/yaml.
  • Add curl -fsSL so a failed fetch errors loudly instead of silently overwriting taskade-public.yaml with an error page / empty file.

Zero-regression

  • Only the fetch:openapi script string changes. No regeneration in this PR → taskade-public.yaml and tools.generated.ts are untouched, so the 57 shipped tools are identical. Verified the new URL returns the v1 OpenAPI doc.

@johnxie
fix(server): point fetch:openapi at the live v1 spec URL
0201752 
The Taskade v1 docs moved: /api/documentation/yaml now 404s; the spec is at
/api/documentation/v1/yaml. Update fetch:openapi (and add curl -fsSL so a failed
fetch errors loudly instead of writing an empty file). No generated output changes
in this PR — it only restores the ability to refresh the v1 spec.
@johnxie
johnxie requested a review from Copilot June 27, 2026 08:27
@changeset-bot

changeset-bot Bot commented Jun 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0201752

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copilot AI reviewed Jun 27, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@johnxie
johnxie merged commit 44580d5 into main Jun 27, 2026
1 of 2 checks passed
@johnxie
johnxie deleted the fix/v1-spec-fetch-url branch June 27, 2026 08:54
@johnxie

johnxie commented Jun 27, 2026

Copy link
Copy Markdown
Member Author

Review follow-up

Ran /pr-review-toolkit:review-pr (code-reviewer) and the /code-review pass. cc @deanzaka @lxcid.

Verdict: no issues. Verified against the live endpoints:

  • old …/api/documentation/yaml → 404 (the breakage this fixes)
  • new …/api/documentation/v1/yaml → 200, openapi: 3.0.3, title "Taskade Public API (v1)"

-fsSL hardening is correct: -f (fail on HTTP error instead of writing an error page), -sS (quiet but still show errors), -L (follow redirects). Build-script-only change — taskade-public.yaml and tools.generated.ts are untouched, so zero regression. No changeset needed (no shipped-code change).

package.json fetch:openapi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@johnxie