Skip to content
CI/CD

Resolve "FutureWarning: xarray.merge will change" (#179) #366

Sign in to view logs

Resolve "FutureWarning: xarray.merge will change" (#179)

Resolve "FutureWarning: xarray.merge will change" (#179) #366

Re-run triggered November 13, 2025 08:57
@btschwertfegerbtschwertfeger
6b01a81
master
Status Success
Total duration 4m 31s
Artifacts 1

cicd.yaml

on: push
Pre-Commit  /  Pre-Commit
18s
Pre-Commit / Pre-Commit
Matrix: CodeQL / Analyze
Matrix: Build
Matrix: Test
Build-Doc  /  Build
1m 5s
Build-Doc / Build
CodeCov  /  Coverage
2m 3s
CodeCov / Coverage
Upload the current release to PyPI  /  Publish Python distribution to PyPI
Upload the current release to PyPI / Publish Python distribution to PyPI
Upload current version to Test PyPI  /  Publish Python distribution to PyPI
14s
Upload current version to Test PyPI / Publish Python distribution to PyPI
https://test.pypi.org/p/python-cmethods
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.