chore(postman): the duplicates are gone and the published collection is current - #33
Merged
Merged
Conversation
…is current The Postman API had 500'd on every /collections endpoint since 2026-09-13, which is why this sat. It recovered, and with GET working a PUT was safe -- the earlier warning was only ever about writing blind while reads were down. Three collections deleted, each backed up first and each proved disposable before deletion rather than after: 0fa5f072 and ba4b5988 were the import duplicates and a request-level diff against the published collection found ZERO requests unique to either; d06c43c2 "My Collection" held Postman's default postman-echo.com samples. One collection remains -- the published 2ee06139, confirmed from the documenter's own <meta name="collectionId"> rather than from a postman.com 200, which is what sent the owner to a dead link last time. The published collection was then re-synced by PUT from the repo file. It had been stale since 2026-09-12 and still carried "the exact source cell behind each value" in the open-data feed description, which the 2026-09-13 wording sweep had corrected in the repo but never pushed. Now 0 occurrences of "source cell", 1 of "source reference", 28 operations intact, documenter and workspace both 200. Two things remain and neither has an API route -- api-keys, me/api-keys, account/api-keys and collections/<uid>/documentation all 404: the published docs TITLE (a Publish-documentation setting, still saying "source cell") and revoking the admin+billing+user key used here. Both recorded with their console paths. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LeaxFttn3GPPVq1yj3Jjuk
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.
The Postman API had 500'd on every
/collectionsendpoint since 2026-09-13, which is why this sat. It has recovered — and withGETworking,PUTwas safe. The earlier warning was only ever about writing blind while reads were down.Deleted three, backed up all four first
0fa5f072ba4b5988d06c43c2postman-echo.comsamplesOne remains: the published
2ee06139— confirmed from the documenter's own<meta name="collectionId">, not from apostman.com200, which is what sent the owner to a dead link last time.Documenter and workspace both 200 immediately after the deletions.
Re-synced the published collection
It had been stale since 2026-09-12 and still carried "the exact source cell behind each value" in the open-data feed description — the 2026-09-13 wording sweep corrected the repo file but never pushed it.
Still pending — console only
api-keys,me/api-keys,account/api-keysandcollections/<uid>/documentationall return 404, so neither of these can be done from a script:<title>,og:titleandtwitter:title. A Publish-documentation setting, so no sweep or re-import reaches it. Suggested: "…with their source reference". Low urgency: the page isnoindex.admin,billing,user(confirmed via/me). Revoke atgo.postman.co/settings/me/api-keys.🤖 Generated with Claude Code
https://claude.ai/code/session_01LeaxFttn3GPPVq1yj3Jjuk