Skip to content
Create Release

fix: authorize front-end RPC calls with the Prividium session token (… #357

Sign in to view logs

fix: authorize front-end RPC calls with the Prividium session token (…

fix: authorize front-end RPC calls with the Prividium session token (… #357

Triggered via push August 27, 2026 19:12
@bxpanabxpana
pushed ffe2b04
main
Status Success
Total duration 22m 5s
Artifacts 5

release.yml

on: push
Create Release Version
7m 0s
Create Release Version
Deploy Block Explorer backend to staging
12m 17s
Deploy Block Explorer backend to staging
Deploy Block Explorer frontend to staging
1m 1s
Deploy Block Explorer frontend to staging
SBOM  /  Create or verify Dependency Track collection project
10s
SBOM / Create or verify Dependency Track collection project
SBOM  /  Generate and upload SBOM of the source code for analysis
14s
SBOM / Generate and upload SBOM of the source code for analysis
Matrix: SBOM / Generate and upload SBOM of the container images for analysis
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
Create Release Version
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Deploy Block Explorer frontend to staging
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: dsaltares/fetch-gh-release-asset@aa2ab1243d6e0d5b405b973c89fa4d06a2d0fff7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: packages/app/Dockerfile#L49
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: packages/app/Dockerfile#L49
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Legacy key/value format with whitespace separator should not be used: packages/data-fetcher/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/data-fetcher/Dockerfile#L36
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/worker/Dockerfile#L36
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/worker/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/api/Dockerfile#L36
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/api/Dockerfile#L33
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: packages/api/Dockerfile#L30
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Deploy Block Explorer backend to staging
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size Digest
matter-labs~block-explorer~J88CRQ.dockerbuild
88.2 KB
sha256:05a9f6f323595d3f7e9e5bf88803ef0e714298a7c72c54f8f9726ac128fa5f29
matter-labs~block-explorer~RWLQUR.dockerbuild
70 KB
sha256:478a9ac2215440d51bdeed77cca7471f16dd280577d240dd9207ab76021e9eed
matter-labs~block-explorer~SULK18.dockerbuild
108 KB
sha256:c4dea24b43d0d9e999ce26343116fb397637115fb5c87d4e8c9904bffe84be84
matter-labs~block-explorer~VSU9N0.dockerbuild
121 KB
sha256:a5872a23ae2e60eb0a7612937ab7a1641bf61331cc6e438b278277cf3c116f9b
matter-labs~block-explorer~ZB64HL.dockerbuild
107 KB
sha256:7f47c9635ce36f370e157d87125ac7211ce34507013e07781b9a26123164c40f