Release v0.12.2 #23
sauljabinrelease.yml
on: push
prepare
0s
build-lhctl
22s
publish-docker
/
lh-canary
2m 13s
publish-docker
/
lhctl
4m 39s
publish-docker
/
lh-dashboard
1m 48s
publish-docker
/
lh-server
1m 52s
publish-docker
/
lh-standalone
6m 36s
publish-java-libraries
10s
publish-sdk-python
30s
publish-sdk-js
19s
publish-sdk-dotnet
26s
create-release
0s
Annotations
3 errors, 9 warnings, and 5 notices
|
publish-java-libraries
Process completed with exit code 2.
|
|
publish-sdk-js
Process completed with exit code 1.
|
|
publish-sdk-dotnet
Process completed with exit code 1.
|
|
prepare
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-lhctl
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
publish-docker / build-server
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
publish-java-libraries
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
publish-sdk-js
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
publish-sdk-dotnet
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):
|
|
Published Docker Image
ghcr.io/littlehorse-enterprises/littlehorse/lh-dashboard:0.12.2
|
|
Published Docker Image
ghcr.io/littlehorse-enterprises/littlehorse/lh-canary:0.12.2
|
|
Published Docker Image
ghcr.io/littlehorse-enterprises/littlehorse/lh-server:0.12.2
|
|
Published Docker Image
ghcr.io/littlehorse-enterprises/littlehorse/lhctl:0.12.2
|
|
Published Docker Image
ghcr.io/littlehorse-enterprises/littlehorse/lh-standalone:0.12.2
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
canary-jar
|
115 MB |
|
|
lhctl
|
27.8 MB |
|
|
server-jar
|
108 MB |
|