• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Ouranosinc / xclim / 41702131257 / 8
90%
main: 90%

Build:
DEFAULT BRANCH: main
Ran 03 Nov 2026 07:32PM UTC
Files 63
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Nov 2026 07:19PM UTC coverage: 86.369%. Remained the same
41702131257.8

push

github

web-flow
Dependency and security updates, SLSA Attestations (#2455)

<!--Please ensure the PR fulfills the following requirements! -->
<!-- If this is your first PR, make sure to add your details to the
AUTHORS.rst! -->
### Pull Request Checklist:
- [ ] This PR addresses an already opened issue (for bug fixes /
features)
    - This PR fixes #xyz
- [ ] Tests for the changes have been added (for bug fixes / features)
- [x] (If applicable) Documentation has been added / updated (for bug
fixes / features)
- [x] CHANGELOG.rst has been updated (with summary of main changes)
- [x] Link to issue (:issue:`number`) and pull request (:pull:`number`)
has been added

### What kind of change does this PR introduce?

* Splits the PyPI/TestPyPI publishing workflows to ensure that the
publishing step is sanitized
* `tag-testpypi.yml` now stages the GitHub release with the attestation
files used for TestPyPI
* Adds the `actions/attest` action to automatically add SLSA
attestations to releases on GitHub
* Updates a few dependencies in CI environment to address security
advisories
* Updates `pytest` to v9.2+ and modifies the doctest call to use only
the `src/xclim/testing/conftest.py` setup file

### Does this PR introduce a breaking change?

Not really. Doctests triggered via `tox` were already skipping `pytest`
v9.1 due to issues with `conftest.py` discoverability. This change
removes that workaround.

Splitting the release workflow such that the
`pypa/gh-action-pypi-publish` step does not compile/build packages is
generally seen as a good idea.

The attestations generated by `actions/attest` are not technically
required, but provide another means for users to validate build
provenance of packages. This is likely much more useful for workflows
generating binaries or OCI images (Docker), but it doesn't hurt to have
it.

### Other information:

https://github.com/pytest-dev/pytest/issues/14683
https://docs.pypi.org/attestations/

Due to our release process, the artifacts used to ... (continued)

7762 of 8987 relevant lines covered (86.37%)

0.86 hits per line

Source Files on job run-3.14-ubuntu-latest- - 41702131257.8
  • Tree
  • List 63
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 41702131257
  • 4047500b on github
  • Prev Job for on main (#40381894137.6)
  • Next Job for on main (#41705692976.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc