ci: add PyPI publishing workflow and release-please config#10
Merged
Conversation
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against dad913b |
beep boop
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
2 participants
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.
Contributes to #6
0.1.0,bootstrap-shapinned past the initial commits). The release-please workflow itself is handled by the org GitHub App..github/workflows/publish.yml: tag-triggered, splits build from publish.buildjob runsmake build, attachesdist/*to the GitHub release (gh release upload), and uploads adistartifact for the publish job.publishjob downloads the artifact and publishes to PyPI via OIDC trusted publishing (environment: pypi,id-token: write). No PyPI tokens in the repo.make buildtarget wrappinguv build.pyproject.tomlto0.1.0so it matches the release-please manifest.LICENSEThe
pypiGitHub environment has already been created on this repo via the API.Test plan
Flagsmith/flagsmith-sql-flag-engine, workflowpublish.yml, environmentpypi.publish.yml, dist assets show up on the GitHub release, and the package lands on PyPI.