Skip to content

Merge pull request #801 from microsoftgraph/release-please--branches-… #44

Merge pull request #801 from microsoftgraph/release-please--branches-…

Merge pull request #801 from microsoftgraph/release-please--branches-… #44

Triggered via push January 14, 2025 09:13
Status Success
Total duration 7m 57s
Artifacts

publish.yml

on: push
Matrix: build / build
build  /  check-build-matrix
0s
build / check-build-matrix
Publish distribution to PyPI
20s
Publish distribution to PyPI
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
samwelkanda
deleted by samwelkanda Jan 14, 2025
pypi_prod

Annotations

8 warnings
build / build (3.11)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build / build (3.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build / build (3.9)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build / build (3.10)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build / check-build-matrix
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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.
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
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):