Skip to content
NextJS build and release

build(deps): bump @vercel/analytics from 1.4.1 to 1.5.0 #2500

Sign in to view logs

build(deps): bump @vercel/analytics from 1.4.1 to 1.5.0

build(deps): bump @vercel/analytics from 1.4.1 to 1.5.0 #2500

Triggered via push February 11, 2025 04:58
@dependabotdependabot[bot]
pushed 8219182
dependabot-npm_and_yarn-development-vercel-analytics-1.5.0
Status Success
Total duration 5m 13s
Artifacts 4

build.yaml

on: push
install
1m 0s
install
prepare-docker-build
51s
prepare-docker-build
lint
1m 2s
lint
Matrix: docker-build-image
verify job matrix results
0s
verify job matrix results
semantic-release
0s
semantic-release
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
install
Cache not found for keys: node-cache-Linux-x64-pnpm-40c3eb9771088385c2929d422ad38f1879903b7f53e40cc3f713ade180b3df54
docker-build-image (1.1.0-development.4, false) / Docker Build and Push
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Legacy key/value format with whitespace separator should not be used: dockerfile#L88
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#L109
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#L111
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/
docker-build-image (latest, false) / Docker Build and Push
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Legacy key/value format with whitespace separator should not be used: dockerfile#L88
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#L109
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#L111
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/
docker-build-image (nightly, false) / Docker Build and Push
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Legacy key/value format with whitespace separator should not be used: dockerfile#L111
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#L88
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#L109
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/
docker-build-image (dependabot-npm_and_yarn-development-vercel-analytics-1.5.0, false) / Docker Build and Push
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Legacy key/value format with whitespace separator should not be used: dockerfile#L88
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#L109
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#L111
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
Clumsy-Coder~exercise-tracker~CR9YMV.dockerbuild
55 KB
Clumsy-Coder~exercise-tracker~NJJ3ET.dockerbuild
54.7 KB
Clumsy-Coder~exercise-tracker~V9IS7O.dockerbuild
55.2 KB
Clumsy-Coder~exercise-tracker~WZX71F.dockerbuild
55.6 KB