chore: sync WaitSpin public client 0.1.16 source refresh - #7
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: efd90ba2ef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "extension_id": "waitspin.waitspin-vscode", | ||
| "version": "0.1.16", | ||
| "source_commit": "8398aa0730e5a4bb4337cf6f58c4948aba28fb2e", | ||
| "source_commit": "0a0cfdc1a01cc00de71422b48ffb72d1a6f51980", |
There was a problem hiding this comment.
Point provenance to a commit reachable from this revision
When this revision is checked out, npm run waitspin:provenance:check fails because 0a0cfdc1a01cc00de71422b48ffb72d1a6f51980 is a sibling of this commit rather than its ancestor, so the git merge-base --is-ancestor check in scripts/waitspin-public-tree-check.mjs exits nonzero. Bind the provenance in a follow-up commit whose parent is the exported source revision, or otherwise reference an ancestor containing the manifest.
Useful? React with 👍 / 👎.
| @@ -6,9 +6,8 @@ | |||
| "open_vsx_url": "https://open-vsx.org/extension/waitspin/waitspin-vscode", | |||
| "open_vsx_verified": true, | |||
| "open_vsx_published_by": "nttylock", | |||
There was a problem hiding this comment.
Preserve the required namespace field in schema v1
Consumers of /status/waitspin-vscode-open-vsx.json that follow the repository's WaitSpinVscodeOpenVsxStatus contract will now receive no namespace_access value even though the payload still declares schema version 1 and the type in lib/waitspin/vscode-marketplace-status.ts requires this property. Keep the field, or version/update the contract so clients do not silently receive undefined for a required status attribute.
Useful? React with 👍 / 👎.
Why\n\n- Scheduled WaitSpin Public Sync run 31480971434 found the curated public export stale.\n- npm, Marketplace, Open VSX, and the canonical VSIX remain on 0.1.16; only the public export/status provenance drifted.\n\n## How\n\n- Regenerate the allowlisted public export manifest and current Open VSX status.\n- Bind provenance to exact exported-source commit 0a0cfdc in a provenance-only second commit.\n\n## Tests\n\n- npm ci\n- npm run waitspin:ci\n- deterministic VSIX SHA-256: 34943ce5c127ab56fde66662adece313915e553ffa45c9f4cd81e0aabc1c720f