K Framework Release v7.1.169 #1528
Triggered via release
October 31, 2024 03:09
rv-jenkins
prereleased
v7.1.169
Status
Success
Total duration
46m 37s
Artifacts
4
release.yml
on: release
Set Release ID
0s
Create source tarball
38s
K Ubuntu Jammy Package
15m 47s
Matrix: k-framework-binary cachix release
K Ubuntu Noble Package
35m 28s
GitHub Pages deployment
8m 20s
Notify Dependents
10s
Annotations
5 errors and 10 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.
|
k-framework-binary cachix release (ubuntu-24.04, ubuntu-24.04)
No push credentials found. Ignoring the 'useDaemon' option.
|
Build MacOS Package
These files were overwritten during the `brew link` step:
|
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.169.arm64_sonoma.bottle.1156.tar.gz'.
No checksum was provided.
For your reference, the checksum is:
sha256 "42d158b89c7f65e391903704b33d6d00ece6d88dde0a57a73a44621a0a254e6a"
|
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):
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
homebrew
|
356 MB |
|
kframework_amd64_ubuntu_jammy.deb
|
175 MB |
|
kframework_amd64_ubuntu_noble.deb
|
174 MB |
|
pyk-docs
|
8.39 MB |
|