ci-release #14348
rootulpci-release.yml
on: merge_group
Matrix: test / go-test
goreleaser
/
goreleaser-check
test
/
test-fibre
1m 33s
test
/
build-e2e-image
4m 44s
lint
/
golangci-lint
46s
lint
/
golangci-lint-fibre
36s
lint
/
hadolint
13s
lint
/
go-mod-tidy-check
44s
lint
/
yamllint
5s
markdown-linter
/
markdown-lint
0s
markdown-linter
/
markdown-link-check
0s
build
/
build
1m 55s
build
/
build-fibre
1m 38s
test
/
test-short
0s
test
/
test-multiplexer
56s
goreleaser
/
goreleaser
test
/
test
3s
Matrix: test / test-docker-e2e
Annotations
27 errors and 18 warnings
|
test / test-multiplexer
Process completed with exit code 2.
|
|
test / test-multiplexer:
internal/embedding/data_linux_amd64.go#L23
pattern celestia-app_linux_v8_amd64.tar.gz: no matching files found
|
|
test / test-docker-e2e (TestStateSyncWithAppUpgrade)
Process completed with exit code 2.
|
|
test / test-docker-e2e (TestE2ESimple)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestE2ESimple)
The operation was canceled.
|
|
test / test-docker-e2e (TestHyperlaneZKIsmStateTransition, TestHyperlaneTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestHyperlaneZKIsmStateTransition, TestHyperlaneTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestHyperlaneZKIsmStateMembership, TestHyperlaneTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestHyperlaneZKIsmStateMembership, TestHyperlaneTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestE2EFullStackPFB)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestE2EFullStackPFB)
The operation was canceled.
|
|
test / test-docker-e2e (TestHyperlaneTokenTransfer, TestHyperlaneTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestHyperlaneTokenTransfer, TestHyperlaneTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestIBC, TestIBCTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestIBC, TestIBCTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestUpgradeLatest)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestUpgradeLatest)
The operation was canceled.
|
|
test / test-docker-e2e (TestPFMMultiHop, TestPFMTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestPFMMultiHop, TestPFMTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestStateSync)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestStateSync)
The operation was canceled.
|
|
test / test-docker-e2e (TestHyperlaneForwarding, TestHyperlaneTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestHyperlaneForwarding, TestHyperlaneTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestICA, TestIBCTestSuite)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestICA, TestIBCTestSuite)
The operation was canceled.
|
|
test / test-docker-e2e (TestMinorVersionCompatibility)
The strategy configuration was canceled because "test.test-docker-e2e.TestStateSyncWithAppUpgra" failed
|
|
test / test-docker-e2e (TestMinorVersionCompatibility)
The operation was canceled.
|
|
lint / yamllint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/get-diff-action@f27caffdd0fb9b13f4fc191c016bb4e0632844af. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / hadolint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: technote-space/get-diff-action@f27caffdd0fb9b13f4fc191c016bb4e0632844af. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / golangci-lint-fibre
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00, technote-space/get-diff-action@f27caffdd0fb9b13f4fc191c016bb4e0632844af. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / go-mod-tidy-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
lint / golangci-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00, technote-space/get-diff-action@f27caffdd0fb9b13f4fc191c016bb4e0632844af. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / test-multiplexer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/app/test, TestBigBlob.*|TestStandardSDK.*)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/tools/chainbuilder)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/app/test, TestSquareSize.*|TestPriority.*)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/app/test, TestIntegration.*)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / test-fibre
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/fibre/..., fibre)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / build-fibre
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/test/ledger)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (unit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/test/txsim)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
test / go-test (github.com/celestiaorg/celestia-app/v9/pkg/user)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@44694675825211faa026b3c33043df3e48a5fa00. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
e2e-image
Expired
|
469 MB |
sha256:8671ef5f1130de5df156c6172ba842b2f78250360b595456412ac53ca8b0c8e6
|
|