Skip to content

[API] Deprecate legacy Workers KV /workers/namespaces/* routes#30756

Open
pmiguel wants to merge 1 commit into
cloudflare:productionfrom
pmiguel:pleal/deprecate-legacy-kv-routes
Open

[API] Deprecate legacy Workers KV /workers/namespaces/* routes#30756
pmiguel wants to merge 1 commit into
cloudflare:productionfrom
pmiguel:pleal/deprecate-legacy-kv-routes

Conversation

@pmiguel

@pmiguel pmiguel commented May 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Deprecate the legacy /accounts/{account_id}/workers/namespaces/* routes in favor of the documented /accounts/{account_id}/storage/kv/namespaces/* routes. The two route sets are interchangeable; migration only requires updating the URL path.

Documentation checklist

@pmiguel pmiguel force-pushed the pleal/deprecate-legacy-kv-routes branch 4 times, most recently from 5eff234 to e9255e3 Compare May 19, 2026 16:56
@pmiguel pmiguel force-pushed the pleal/deprecate-legacy-kv-routes branch from e9255e3 to bdd887b Compare June 1, 2026 11:39
@pmiguel pmiguel force-pushed the pleal/deprecate-legacy-kv-routes branch from bdd887b to 55e9024 Compare June 3, 2026 14:43
@pmiguel pmiguel marked this pull request as ready for review June 11, 2026 10:52
@pmiguel pmiguel requested review from a team as code owners June 11, 2026 10:52
@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Review

⏸️ Automatic reviews for this PR are paused.

This PR has already received 2 automatic reviews. To run another review, a codeowner can comment /review or /full-review.

Tip: Keep PRs in draft mode until they are ready for review — the bot skips draft PRs automatically.


💡 0 suggestions found in commit 6e32fad.

Acknowledged by author (1)
File Issue Note
changelog/kv/2026-06-08-kv-legacy-namespace-routes-deprecation.mdx line 15 Oxford comma No objection was made about the comma style. The vy-ton comment focuses on verifying content accuracy and providing clear API alternatives rather than grammar conventions.
Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.

@bodolaigyorgy3-blip

Copy link
Copy Markdown
BTC_bc1qhlg2rxefvx4zjp5sl9ghwsg9rywzh32q7j4xg3 (1)

@bodolaigyorgy3-blip

Copy link
Copy Markdown

bitcoin:BC1QHLG2RXEFVX4ZJP5SL9GHWSG9RYWZH32Q7J4XG3

@bodolaigyorgy3-blip

Copy link
Copy Markdown

0x71C7656EC7ab88b098defB751B7401B5f6d8976F

@bodolaigyorgy3-blip

Copy link
Copy Markdown

bc1q8cqrm7mq65upr4wtx7csn6tk5uq2ux2gc0t4lw

@bodolaigyorgy3-blip

Copy link
Copy Markdown

@bodolaigyorgy3-blip

Copy link
Copy Markdown

UQBlQ5HtXzJfAQ62SW-j1ZE3T3pLD2rxNC4dtqh10CBWf5-h

@vy-ton

vy-ton commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

/bonk please review, make sure changelog has clear alternative that user should use instead of deprecated API endpoints

@ask-bonk ask-bonk Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The changelog entry clearly identifies the alternative routes (/storage/kv/namespaces/*) and provides a concrete migration example. Good work on making the path substitution explicit.

One suggestion: the api-deprecations.yaml entry could be more helpful by listing the replacement routes explicitly, matching the style used by most other entries in that file (e.g., Zero Trust Devices, Radar endpoints, Cloudflare Images). Since the migration is a direct prefix swap, listing the equivalents makes it easier for users to verify their integrations at a glance.

Comment thread src/content/release-notes/api-deprecations.yaml Outdated
@ask-bonk

ask-bonk Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Posted a review on PR #30756.

Summary:

  • The changelog entry does clearly identify the alternative (/storage/kv/namespaces/*) and explains that migration is a simple prefix swap (/workers/namespaces//storage/kv/namespaces/), with a concrete code example.
  • I left one suggestion on api-deprecations.yaml: the "Replacements" section currently just points readers to the full API docs. Other entries in that same file (e.g., Zero Trust Devices, Radar endpoints) list replacement routes explicitly. Since these are direct equivalents, I suggested mirroring the deprecated API list with the replacement paths to make migration easier for users cross-referencing their integrations.

github run

@pmiguel pmiguel force-pushed the pleal/deprecate-legacy-kv-routes branch 2 times, most recently from 6e32fad to 963e839 Compare June 11, 2026 18:03
Deprecate the legacy /accounts/{account_id}/workers/namespaces/*
routes in favor of the documented /accounts/{account_id}/storage/kv/namespaces/*
routes. The two route sets are interchangeable; migration only requires
updating the URL path.
@pmiguel pmiguel force-pushed the pleal/deprecate-legacy-kv-routes branch from 963e839 to 7c98e1f Compare June 16, 2026 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants