add auto pypi release #34
Merged
Conversation
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
- Add GitHub Actions workflow for automated PyPI releases on git tags - Support TestPyPI releases for branches starting with test-release- - Uses trusted publishing (OIDC) for secure authentication - Include comprehensive testing and linting before release
- Separate jobs for TestPyPI and PyPI publishing - Use GitHub environments for better security control - TestPyPI: publishes on test-release-* branches - PyPI: publishes only on version tags (v*) - Follow packaging.python.org recommendations - Use trusted publishing with OIDC tokens
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #34 +/- ##
=======================================
Coverage 84.34% 84.34%
=======================================
Files 14 14
Lines 492 492
=======================================
Hits 415 415
Misses 77 77 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…rsion - Remove testpypi environment requirement (not configured yet) - Add verbose logging and file listing for debugging - Update version to 1.3.1.dev1 to avoid conflicts - Add print-hash for better visibility
- Add continue-on-error to TestPyPI step - Provide clear instructions for trusted publishing setup - Workflow will complete successfully even if TestPyPI fails - Gives guidance on configuring trusted publisher
- Re-add testpypi environment (may be required by trusted publisher config) - Add detailed environment and file debugging - Remove continue-on-error to see actual failure - Debug GitHub context variables and distribution files
- Use python-package-distributions artifact name (matches working example) - Simplify permissions to only id-token: write - Match naming conventions from working 20c/rdap workflow - Remove verbose flags that might cause issues
- Aligned with working 20c/rdap workflow structure - TestPyPI issues may be on their side (trusted publishing configured) - Workflow structure is solid and ready for main branch - Production PyPI release can be tested with version tags
…atch Per PyPI troubleshooting docs, environment name must match exactly. Testing without environment in case TestPyPI config has blank environment name.
TestPyPI config now matches: - Workflow: release.yaml - Environment: testpypi
- Fix trailing whitespace issues - Uncomment testpypi environment to match corrected TestPyPI config
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.
No description provided.