docs: add Releasing section to CONTRIBUTING, tidy root - #202
Merged
Conversation
…e out of root Root markdown was getting crowded ahead of directory/press traffic. Document the per-release flow (tag, PyPI publish, MCP Registry, extension) where maintainer workflow already lives, and relocate the stale internal pilot-readiness note to research/notes/.
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.
What
## Releasingsection to the end ofCONTRIBUTING.mddocumenting the per-version flow: version bump, changelog, tag-triggered PyPI publish + GitHub Release (tag must matchpyproject.toml), clean-venv verification of bothredcon --versionandimport redcon; redcon.__version__(the path that regressed in 1.11.0), plus the MCP Registry (server.json+mcp-publisher) and VS Code (vsce publish) steps.pilot-readiness.md(last updated 2026-03-15) out of the repo root intoresearch/notes/, where internal notes already live.Why
Release process is maintainer workflow, so it belongs in CONTRIBUTING next to Setup / Guidelines / Pull Requests rather than a new root file. And the root should be clean for directory and press traffic.
Note
Step 6 assumes
server.jsonlands in the repo root - that will follow as its own small PR aftermcp-publishervalidation.