Repository navigation
Update CI actions and run full CI once per change - #38
Merged
Merged
Conversation
Updates the requirements on [dtolnay/rust-toolchain](https://github.com/dtolnay/rust-toolchain), [actions/setup-python](https://github.com/actions/setup-python), [PyO3/maturin-action](https://github.com/pyo3/maturin-action) and [peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages) to permit the latest version. Updates `dtolnay/rust-toolchain` to cfcaf53ba4c621917ec7f78a66bff7a8848ddad4 - [Release notes](https://github.com/dtolnay/rust-toolchain/releases) - [Commits](https://github.com/dtolnay/rust-toolchain/commits/cfcaf53ba4c621917ec7f78a66bff7a8848ddad4) Updates `actions/setup-python` from 6.3.0 to 7.1.0 - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@ece7cb0...6d4fd22) Updates `PyO3/maturin-action` from 423a6347767a8b16e65c2a7a7042e4a921528da8 to e83996d129638aa358a18fbd1dfb82f0b0fb5d3b - [Release notes](https://github.com/pyo3/maturin-action/releases) - [Commits](PyO3/maturin-action@423a634...e83996d) Updates `peaceiris/actions-gh-pages` from 329bcc8f12caed2cefe5a5b80781499a6f3b361b to 84c30a85c19949d7eee79c4ff27748b70285e453 - [Release notes](https://github.com/peaceiris/actions-gh-pages/releases) - [Changelog](https://github.com/peaceiris/actions-gh-pages/blob/main/CHANGELOG.md) - [Commits](peaceiris/actions-gh-pages@329bcc8...84c30a8) --- updated-dependencies: - dependency-name: dtolnay/rust-toolchain dependency-version: cfcaf53ba4c621917ec7f78a66bff7a8848ddad4 dependency-type: direct:production dependency-group: github-actions - dependency-name: actions/setup-python dependency-version: 7.1.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: PyO3/maturin-action dependency-version: e83996d129638aa358a18fbd1dfb82f0b0fb5d3b dependency-type: direct:production dependency-group: github-actions - dependency-name: peaceiris/actions-gh-pages dependency-version: 84c30a85c19949d7eee79c4ff27748b70285e453 dependency-type: direct:production dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Drop the push-to-main trigger (docs.yml still deploys on main) and add a "CI result" job that fails unless every job succeeded. Branch protection will require it and require PRs to be up to date with main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CarlKCarlK
added a commit
that referenced
this pull request
Nov 14, 2026
Update CI actions and run full CI once per change
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.
Supersedes #37 so the combined change needs only one full CI run.
From #37 (already passed 58/58):
New:
push: maintrigger from ci.yml, so full CI runs on PRs, monthly, and for release tags (release.yml reuses ci.yml) but not again after each merge. Documentation still deploys on main via docs.yml.CI resultjob (if: always()) that fails unless every other job succeeded. Branch protection will require only this check, so an upstream failure can't show up as a skipped (passing) required check.After this merges, branch protection on
mainwill requireCI resultand require branches to be up to date before merging. Admins can still bypass.