Conversation
Drop Contributor Covenant file to keep community expectations lightweight. Ship MkDocs site, SECURITY.md, CITATION.cff, Python 3.13-focused guides, Fiber three-way benchmarks, coverage and regression gates, hatch-vcs versioning, expanded tests, and lazy TestClient import.
Remove Code of Conduct; docs, benchmarks, CI, release automation
- Deploy docs via Pages artifact (configure/upload/deploy) with .nojekyll; document Settings requirement. - MkDocs: site_author, social links, Material repo icon; strict build verified. - README: PyPI/GitHub release badges, docs workflow + branch, website liveness, GitHub Pages link. - CI: ruff/mypy alignment; library typing (ASGIApp), tests override; tox; benchmark compare tweaks.
docs: GitHub Pages via Actions, MkDocs and README badges
Updating the docs workflow.
Sync to stage
- Docs: detect whether Pages is enabled and fail with clear instructions instead of integration errors. - Release: publish dev builds to TestPyPI on master merges; keep real PyPI + Docker + GitHub Release on v* tags.
The Pages API check can fail under token restrictions even when Pages is configured; rely on configure-pages/deploy-pages instead.
Trusted publishing requires PyPI/TestPyPI 'publisher' configuration; use TEST_PYPI_API_TOKEN for TestPyPI dev publishes while keeping OIDC trusted publishing for real PyPI tags.
Avoid fallback to OIDC trusted publishing when the token secret isn't configured.
Disable local version identifiers (+g<hash>) for hatch-vcs so dev builds can be uploaded to TestPyPI.
- Benchmark workflow now runs on stage pushes as well as PRs. - New auto-tag workflow creates vX.Y.Z tags on merged master PRs with release:patch|minor|major labels. - CONTRIBUTING documents release label behavior.
normalize both owner and repo to lowercase for ghcr tags. use skip-existing for TestPyPI and PyPI publishes to avoid rerun failures. Made-with: Cursor
Contributor
Benchmark results
HTTP throughput (FasterAPI vs FastAPI vs Fiber)
Direct ASGI (no HTTP; 50,000 iterations)
Routing (radix vs regex, 1,500,000 lookups)
How to read this
|
Avoid calling the Issues comments API on stage push runs where no PR number exists. Made-with: Cursor
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.
What this fixes
publish-docker: normalize both owner and repository names to lowercase so GHCR tags are valid.publish-testpypiandpublish-pypi: addskip-existing: trueto make reruns safe.Why
repository name must be lowercasein Docker publish.