Skip to content

DX-596-together-dedicated-endpoints: sync with mintlify-docs#1258 - #60

Open
zainhas wants to merge 1 commit into
mainfrom
docs-sync/together-dedicated-endpoints/mintlify-docs-pr-1258
Open

DX-596-together-dedicated-endpoints: sync with mintlify-docs#1258#60
zainhas wants to merge 1 commit into
mainfrom
docs-sync/together-dedicated-endpoints/mintlify-docs-pr-1258

Conversation

@zainhas

@zainhas zainhas commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Syncs together-dedicated-endpoints with togethercomputer/mintlify-docs#1258 (MLE-6650).

Changed docs that triggered this

  • docs/dedicated-endpoints/migrate-from-v1.mdx — reframes the guide to reflect that v1 create and restart are retired, adds a Troubleshooting section mapping the new endpoints_v1_create_access_disabled (HTTP 403) error to its v2 fixes, and hedges the v1 support window to "until further notice."

Skill changes

  • SKILL.md: Add a high-signal rule at the top of High-Signal Rules stating v1 create and restart are disabled, listing the API/SDK/CLI surfaces that now return endpoints_v1_create_access_disabled (HTTP 403), and pointing agents at the v2 deploy flow (tg beta endpoints deploy, together>=2.24.0).
  • SKILL.md: Note the together>=2.24.0 floor for v2 endpoint creation alongside the existing together>=2.0.0 base SDK requirement.
  • SKILL.md: Add the Migrate from v1 guide to Official Docs.
  • references/api-reference.md: Prepend a Warning callout mirroring the migration guide (v1 create/restart disabled, v2 deploy command, together>=2.24.0) so agents reading the reference see the retirement before hitting the v1 Create Endpoint section.
  • references/api-reference.md: Add two rows to the Troubleshooting table covering the endpoints_v1_create_access_disabled error and the "stopped v1 endpoint won't restart" case, each linking to the migration guide.

Not touched

The existing v1 scripts (scripts/manage_endpoint.py, scripts/deploy_finetuned.py, scripts/upload_custom_model.py, scripts/manage_endpoint.ts) and the bulk of references/api-reference.md still describe the v1 flow. Running v1 endpoints continue to serve until further notice, and #1258 doesn't add or replace any v2 SDK/API surface docs — a full v2 rewrite is a separate effort out of scope for this minimal, PR-scoped sync.


Generated by the Sync Skills Cursor Automation. Please review before merging.

- Add high-signal rule flagging v1 create/restart disablement (returns
  endpoints_v1_create_access_disabled HTTP 403) and pointing to the v2
  deploy flow (tg beta endpoints deploy, together>=2.24.0).
- Note the together>=2.24.0 floor for v2 endpoint creation alongside the
  existing together>=2.0.0 base requirement.
- Link the Migrate from v1 guide under Official Docs.
- Prepend a Warning callout to references/api-reference.md and add two
  Troubleshooting rows covering the disabled v1 create/restart paths.

Sourced from togethercomputer/mintlify-docs#1258 (MLE-6650). No script
or v1-flow changes; scripts and reference bodies still describe the
existing v1 API surface which continues to serve running endpoints.
@zainhas
zainhas requested a review from atihkin July 17, 2026 00:06
@broly-code-security-scanner

Copy link
Copy Markdown

Broly Security Scan

Note

Clean scan
No vulnerabilities detected in this PR.

Note

Re-scan this PR anytime with /broly scan — useful after /broly undismiss, or to refresh findings without a new push.

Broly — SAST (zai-org/GLM-5.2) · Secrets · SCA · GH Actions (zizmor) · Containers · SBOM · Powered by Together AI

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.

2 participants