K Framework Release v7.1.31 #1375
tothtamas28release.yml
on: release
Set Release ID
0s
Create source tarball
50s
K Ubuntu Jammy Package
25m 8s
Matrix: k-framework-binary cachix release
GitHub Pages deployment
3m 23s
Notify Dependents
9s
Annotations
6 errors and 8 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.
|
|
GitHub Pages deployment
Process completed with exit code 1.
|
|
k-framework-binary cachix release (MacM1, self-macos-12)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: workflow/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
k-framework-binary cachix release (ubuntu-24.04, ubuntu-24.04)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: workflow/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
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
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
|
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
|