Skip to content

Auto Release

Auto Release #13

Triggered via schedule October 30, 2025 02:41
Status Success
Total duration 1m 26s
Artifacts

auto-release.yml

on: schedule
check-and-release
6s
check-and-release
Matrix: Trigger Release Workflow / Run Tests / test
Trigger Release Workflow  /  ...  /  lint
21s
Trigger Release Workflow / Run Tests / lint
Trigger Release Workflow  /  Create Release
8s
Trigger Release Workflow / Create Release
Trigger Release Workflow  /  Build and Publish
20s
Trigger Release Workflow / Build and Publish
Trigger Release Workflow  /  Server repo PR
16s
Trigger Release Workflow / Server repo PR
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Trigger Release Workflow / Create Release
"pull_request_target.edited" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Trigger Release Workflow / Create Release
"pull_request_target.synchronize" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Trigger Release Workflow / Create Release
"pull_request_target.reopened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
Trigger Release Workflow / Create Release
"pull_request_target.opened" is not a known webhook name (https://developer.github.com/v3/activity/events/types/)
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.