Repository navigation
ci: release automatically through core's release workflow - #423
Merged
Merged
Conversation
Each squash merge that changes a non-plugin file releases at the level its PR title gives. Depends on brain-score/core#180.
KartikP
marked this pull request as ready for review
October 9, 2026 10:20
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
1 participant
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.
Makes language releases fully automatic, using the shared workflows added in brain-score/core#180.
Depends on brain-score/core#180. Both workflows here call
brain-score/core/.github/workflows/*.yml@main, which do not exist until that PR merges. Do not merge this first. The human setup steps (GitHub App, org secrets,pypienvironment, ruleset, PyPI trusted publisher) are in the setup guide and are not part of this PR.Changes
release.yml(new): on each push tomain, calls core's reusable release workflow withrelease-paths: ^brainscore_language/(?!(models|benchmarks|data|metrics)/), so plugin-only merges never release. The PR title type picks the level (featminor,fix/perfpatch, major only with!orBREAKING CHANGEplus themajor updatelabel). The PyPI publish job runs in this file, because PyPI trusted publishing does not work inside a reusable workflow. A manual Run workflow with alevelinput cuts the first release.pr-title.yml(new): calls core's PR-title check; it comments on a bad title with the allowed types.pyproject.toml: adds[tool.semantic_release].Starting version
PyPI and
pyproject.tomlare at 2.2.1, andv2.2.1is the highest tag and is onmain, so the first release is 2.2.2 (patch) or 2.3.0 (minor) with no collision. Pick the level for the manual first run from whatmainhas gained since 2.2.1.