fix(wrangler): version listing limits#14165
Conversation
🦋 Changeset detectedLatest commit: db755e0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Now let me verify the real correctness concern with the non-JSON path and ordering. The change applies the slice to both JSON and table output. The sort orders ascending (oldest first), which preserves the existing display order. Both correct. Let me consider one genuine issue: the PR note says the API "now defaults to 100". But Let me verify there are no other callers of The implementation is correct, well-tested (verifies I find no logic bugs, security issues, backward-compatibility violations, or incorrect API behavior. LGTM |
|
✅ All changesets look good |
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
@cloudflare/wrangler-bundler
commit: |
|
Codeowners approval required for this PR:
Show detailed file reviewers |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
|
Wow that was fast. Thanks @NuroDev ! 🙏 |
Fixes #14160.
This change updates the
wrangler versions listcommand to only show 10 version rather than 100, which the API now defaults to.Note
The API does not allow for both
deployable=trueandper_page=10parameters together. So we filter the versions list client-sode.A picture of a cute animal (not mandatory, but encouraged)