Release from the monorepo mirror - #276
Merged
Merged
Conversation
The code in this repository is generated in Mixedbread's monorepo and mirrored here as one commit per change; a new version arrives with a tag and a GitHub release. CI now lints, type-checks and builds; the publish workflow runs on a published release through trusted publishing (or the PYPI_TOKEN secret) and no longer depends on release-please.
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.
The SDK source now lives in Mixedbread's monorepo, which mirrors every change here as one commit and creates a GitHub release whenever the package version changes. This PR makes the repository's own workflows fit that flow.
Changes
ci.yml: lint, type-check and build on pushes to main and on pull requests (the test suite runs in the monorepo against its mock server before a change is mirrored).publish-*.yml: publish on a published GitHub release through PyPI trusted publishing, using thepypienvironment; thePYPI_TOKENsecret remains as the token fallback..github/CONTRIBUTING.mdexplains that pull requests are ported into the monorepo rather than merged.Before the first release
publish-*.yml, environmentpypi), or set thePYPI_TOKENsecret.uv.lock/ lint scripts differ).