Skip to content

Bump ecto from 3.12.1 to 3.12.2 (#502) #1693

Bump ecto from 3.12.1 to 3.12.2 (#502)

Bump ecto from 3.12.1 to 3.12.2 (#502) #1693

Triggered via push August 26, 2024 12:47
Status Success
Total duration 13m 16s
Artifacts 2

ci.yaml

on: push
Elixir dependencies
5m 1s
Elixir dependencies
Rebuild main branch dependencies
2s
Rebuild main branch dependencies
Lint checks
14s
Lint checks
Generate project documentation
2m 42s
Generate project documentation
Matrix: API bc check
Build and push container images
4m 15s
Build and push container images
Build the docker image for the demo environment
4m 0s
Build the docker image for the demo environment
Commit the container image on OBS
3m 33s
Commit the container image on OBS
Commit the RPM package on OBS
3m 33s
Commit the RPM package on OBS
Fit to window
Zoom out
Zoom in

Annotations

39 warnings
Generate project documentation
The following actions uses node12 which is deprecated and will be forced to run on node16: lee-dohm/generate-elixir-docs@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Generate project documentation
The following actions use a deprecated Node.js version and will be forced to run on node20: lee-dohm/generate-elixir-docs@v1, Legion2/swagger-ui-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Generate project documentation
use Bitwise is deprecated. import Bitwise instead
Generate project documentation
Logger.warn/1 is deprecated. Use Logger.warning/2 instead
Generate project documentation
documentation references type "Trento.Checks.V1.ExecutionRequested.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.FactsGathered.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.ExecutionRequested.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.FactsGathered.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.ExecutionStarted.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.ExecutionRequested.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.FactsGathered.t()" but it is hidden or private
Generate project documentation
documentation references type "Trento.Checks.V1.ExecutionRequested.t()" but it is hidden or private
Elixir dependencies
use Bitwise is deprecated. import Bitwise instead
Elixir dependencies
Logger.warn/1 is deprecated. Use Logger.warning/2 instead
Commit the container image on OBS
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Commit the container image on OBS
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Commit the container image on OBS
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/
Commit the container image on OBS
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/
Commit the container image on OBS
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/
Commit the container image on OBS
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/
Commit the container image on OBS
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/
Commit the RPM package on OBS
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Commit the RPM package on OBS
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Commit the RPM package on OBS
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/
Commit the RPM package on OBS
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/
Commit the RPM package on OBS
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/
Commit the RPM package on OBS
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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L2
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: Dockerfile#L3
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: Dockerfile#L4
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: Dockerfile#L24
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: Dockerfile#L25
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: Dockerfile#L26
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: Dockerfile#L4
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: Dockerfile#L24
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: Dockerfile#L25
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: Dockerfile#L26
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: Dockerfile#L2
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: Dockerfile#L3
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/

Artifacts

Produced during runtime
Name Size
trento-project~wanda~860E1G.dockerbuild
64.9 KB
trento-project~wanda~VU8UXQ.dockerbuild
38.4 KB