docs: PyPI badge, quick-links nav, roadmap; harden release workflow#32
Merged
Conversation
Now that deepcloak 0.1.0 is live on PyPI, finish the top-tier-repo polish: - PyPI version badge (real) in all three READMEs - Quick-links nav row under the hero (Quickstart · How it works · MCP · Why · Changelog) - 🗺️ Roadmap section inviting Discussions / feature requests - release.yml: skip-existing + gate on PUBLISH_TO_PYPI var so publishing a release before the Trusted Publisher is set is a no-op, never a red ✗ Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Finishes the top-tier-OSS polish now that
deepcloak 0.1.0is live on PyPI (pip install deepcloakworks).skip-existing: true+ gated on aPUBLISH_TO_PYPIrepo variable, so publishing the v0.1.0 GitHub Release before the Trusted Publisher is configured is a no-op (no red ✗). Future releases auto-publish once the var is set.🤖 Generated with Claude Code