K Framework Release v7.1.186 #1546
Triggered via release
December 10, 2024 19:42
rv-jenkins
prereleased
v7.1.186
Status
Success
Total duration
47m 24s
Artifacts
4
release.yml
on: release
Set Release ID
0s
Create source tarball
49s
K Ubuntu Jammy Package
27m 18s
Matrix: k-framework-binary cachix release
K Ubuntu Noble Package
31m 51s
GitHub Pages deployment
8m 31s
Notify Dependents
7s
Annotations
5 errors and 11 warnings
Build MacOS Package
The process '/opt/homebrew/bin/git' failed with exit code 1
|
Build MacOS Package
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
|
Test MacOS Package
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
|
Test MacOS Package
The process '/opt/homebrew/bin/git' failed with exit code 1
|
Publish Release
Process completed with exit code 1.
|
Create source tarball
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
k-framework-binary cachix release (ubuntu-24.04, ubuntu-24.04)
No push credentials found. Ignoring the 'useDaemon' option.
|
Build MacOS Package
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
Build MacOS Package
Unable to clean or reset the repository. The repository will be recreated instead.
|
Test MacOS Package
Unable to clean or reset the repository. The repository will be recreated instead.
|
Test MacOS Package
Cannot verify integrity of 'kframework--7.1.186.arm64_sonoma.bottle.1169.tar.gz'.
No checksum was provided.
For your reference, the checksum is:
sha256 "1c10c5d52c0c28dcff26cd8510f7198b1143684e1b2507510f46b6de5ad11511"
|
Test MacOS Package
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
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):
|
Notify Dependents
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
homebrew
|
357 MB |
|
kframework_amd64_ubuntu_jammy.deb
Expired
|
175 MB |
|
kframework_amd64_ubuntu_noble.deb
Expired
|
174 MB |
|
pyk-docs
Expired
|
8.4 MB |
|