Skip to content

Commit

Permalink
chore(deps): update node.js to v22 (#3)
Browse files Browse the repository at this point in the history
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
  • Loading branch information
renovate[bot] authored Oct 6, 2024
1 parent 590b239 commit ab7258f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM ghcr.io/hazmi35/node:21-dev-alpine as build-stage
FROM ghcr.io/hazmi35/node:22-dev-alpine as build-stage

Check warning on line 1 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker / build

The 'as' keyword should match the case of the 'from' keyword

FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

# Prepare pnpm with corepack (experimental feature)
RUN corepack enable && corepack prepare pnpm@latest
Expand All @@ -22,7 +22,7 @@ RUN pnpm run build
RUN pnpm prune --production

# Get ready for production
FROM ghcr.io/hazmi35/node:21-alpine
FROM ghcr.io/hazmi35/node:22-alpine

LABEL name "discord-sendiri-bot"

Check warning on line 27 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
LABEL maintainer "Stegripe Development <[email protected]>"

Check warning on line 28 in Dockerfile

View workflow job for this annotation

GitHub Actions / docker / build

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Expand Down

0 comments on commit ab7258f

Please sign in to comment.