From a3d645978a6ccef279870498979733682f63e206 Mon Sep 17 00:00:00 2001 From: spypsy Date: Fri, 8 Sep 2023 11:09:21 +0100 Subject: [PATCH] fix: COMMIT_TAG arg value in canary Dockerfile (#2118) This change went in mistakenly, the value should stay empty # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist). --- yarn-project/canary/Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/yarn-project/canary/Dockerfile b/yarn-project/canary/Dockerfile index eace3990aab..fa9498350af 100644 --- a/yarn-project/canary/Dockerfile +++ b/yarn-project/canary/Dockerfile @@ -2,7 +2,7 @@ FROM node:18-alpine RUN apk update && apk add --no-cache udev ttf-freefont chromium curl jq bash ENV CHROME_BIN="/usr/bin/chromium-browser" PUPPETEER_SKIP_CHROMIUM_DOWNLOAD="true" -ARG COMMIT_TAG="v0.1.0-alpha62" +ARG COMMIT_TAG="" #Build canary WORKDIR /usr/src/