Repository navigation
submission-hygiene - #901
Merged
Merged
Conversation
Clean-ups from the v1.0.888 release and the first directory submissions (#900), so the next release and plugin versions run through without surprises. Docs: release process step 10 no longer claims the pin PR runs the full Build (packaging/** is in paths-ignore); step 7a notes Chocolatey's trusted automated moderation; step 11 records where the OpenAI org ID lives, business verification and uploading early to read the validator; step 12 records auto-publish, the push webhook and the by-design holds. The Anthropic submission checklist gains a section on what the validator reports and what to leave alone, the data handling answers as submitted, the webhook mechanics, the surfaces chosen, and ticks the one-time items done on 2026-11-05. Links: https://stackql.io/docs now redirects to the homepage, so every documentation link in the plugins, wrappers, MCPB manifests and registry template points at https://stackql.io/getting-started (provider pages at https://stackql.io/providers). Tooling: render-platforms.sh stamps package-lock.json alongside package.json (the lockfile had been left at 0.12.778); smoke-test.py keeps the launcher's last stderr lines and prints them when the server exits before answering (the Windows ARM64 dotnet flake left no diagnostic); build.yml ignores the release tooling under cicd/python so a tooling fix does not run the Build matrix, and runs the two Docker merge jobs one at a time after two Docker Hub 429s in one day. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
15 of 21 tasks
10 tasks
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
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.
Clean-ups from the v1.0.888 release and the first ChatGPT and Anthropic directory submissions. Works through the actionable items in #900; the items that wait on external replies (demo recording URL, Verified organization, Ubuntu 26.04 re-validation) stay open there.
Docs
docs/stackql_release_process.md: step 10 corrected (the pin PR runsstdio-plugins, themcp-packagingvalidation, Lint and CodeQL;packaging/**is in the Build workflow'spaths-ignore, so the matrix does not run); step 7a notes thatstackqlis a trusted Chocolatey package with automated moderation; step 11 records where the OpenAI organization ID lives, who completes business verification, and uploading the first ZIP early to read the validator (mcp_configuration_excludedmeans the allowlist has not landed); step 12 records the holds that are by design, the answers given at submission, auto-publish and the push webhook.packaging/mcpb/docs/anthropic-submission.md: new section on what the validator reports and what to leave alone (the node launcher hold, the five listing-field warnings, the Verified organization note, the undocumentedclassificationblock); the one-time checklist now records the 2026-11-05 submission (surfaces, data handling answers, compliance contact, webhook) and keeps the reviewer decision and Verified organization open.Links
https://stackql.io/docsredirects to the homepage, so the documentation link in both plugin manifests (and the derived Codex overlay), both plugin READMEs, the shared setup skill and its two vendored copies, the MCPB manifest templates and fixtures, the npm and PyPI READMEs,pyproject.tomland the registryserver.template.jsonnow points athttps://stackql.io/getting-started; the two "provider pages" sentences point athttps://stackql.io/providers. Both plugins were re-rendered at 1.0.888 afterwards and match the committed files.Tooling
packaging/mcpb/scripts/render-platforms.sh: stampspackage-lock.json(top-level andpackages[""]) with the version too; the lockfile had stayed at0.12.778through two releases. Committed here at1.0.888.packaging/mcpb/scripts/smoke-test.py: a second reader thread keeps the launcher's last 40 stderr lines;fail()prints them, and the exit path waits up to a second for them. The dotnet Windows ARM64 flake in the 1.0.888mcp-packagingrun left nothing to diagnose..github/workflows/build.yml:cicd/python/attach_build_artifacts.pyand its test added to bothpaths-ignorelists (a release-tooling fix ran the full matrix in attach-artifacts-utf8 #897);dockermergegetsmax-parallel: 1after both merge variants hit Docker Hub429 Too Many Requeststwice on 2026-11-05.Test plan
python packaging/openai-plugin/scripts/validate.pyandpython packaging/mcpb/scripts/validate-claude-plugin.py: pass.make npm-manifest VERSION=1.0.888after the edits: re-rendered files identical to the committed ones apart from the newly stamped lockfile.python -m py_compile packaging/mcpb/scripts/smoke-test.py,bash -n packaging/mcpb/scripts/render-platforms.sh,js-yaml .github/workflows/build.yml: pass.cicd/pythonunit tests: 9 passed.stdio-plugins(render check,claude plugin validate --strict, smoke tests on four platforms),mcp-packagingvalidation (exercises the smoke test change), and the full Build because the workflow file changed.🤖 Generated with Claude Code