Upgrade dockerimage

[HalvorHaugan]

https://github.com/GoogleContainerTools/distroless/tree/main?tab=readme-ov-file#what-images-are-available

Any other tags are considered deprecated and are no longer updated

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2661ac2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[KenAJoh]

We are currently building all packages with "LTS" version of node

- uses: actions/setup-node@v4
        with:
          node-version: lts/*
          cache: yarn

LTS is currently v20, and v22 won't be LTS until October Should we update the workflow to build everything with latest version of v22? Or just use gcr.io/distroless/nodejs20-debian12?

[HalvorHaugan]

We are currently building all packages with "LTS" version of node

- uses: actions/setup-node@v4
        with:
          node-version: lts/*
          cache: yarn

LTS is currently v20, and v22 won't be LTS until October Should we update the workflow to build everything with latest version of v22? Or just use gcr.io/distroless/nodejs20-debian12?

Good question. On one hand, if we hard code the version in the workflows, we have more places to update. But then we assure consistent versions. On the other hand, if we keep lts we only need to ever update Dockerfile. Do you think there's a risk of errors by using different versions in workflows vs. Docker?