You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i’m very excited for the changes introduced in v3.7.0 to use existing wrangler installation when appropriate (from #271). my app relies on getPlatformProxy so it cannot be deployed with any version of wrangler that doesn’t include that API. however, in my case, the logic to check that existing install and version if somehow falling through to the ⚠️ Wrangler not found or version is incompatible. Installing...fallback logic.
here is my output from the workflow run, which shows that i am using yarn v1.22.22 and shows that /usr/local/bin/yarn wrangler --version, as invoked by wrangler-action, is returning the version number (3.63.2) correctly:
Run cloudflare/wrangler-action@v3.7.0
with:
apiToken: ***
quiet: false
🔍 Checking for existing Wrangler installation
/usr/local/bin/yarn wrangler --version
yarn run v1.22.22
$ /home/runner/work/outlyne/outlyne/node_modules/.bin/wrangler --version
3.63.2
Done in 0.57s.
⚠️ Wrangler not found or version is incompatible. Installing...
📥 Installing Wrangler
/usr/local/bin/yarn add wrangler@3.13.2
yarn add v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
my hypothesis is that the issue is due to the fallback regex starting with the “start of string” token (/^):
i’m not sure how stdout is derived, but if it includes anything before the version output (e.g. \n3.63.2, or even /home/runner/work/outlyne/outlyne/node_modules/.bin/wrangler --version\n3.63.2), the regex won’t match it.
the most obvious solution, then, is to use multi-line mode so that ^ matches the start of every line as well as the start of the string:
acusti
changed the title
Install version of wrangler not being used with v3.7.0
Installed version of wrangler not being used with v3.7.0 using yarn v1.22.22 in CI
Jul 11, 2024
i’m very excited for the changes introduced in v3.7.0 to use existing wrangler installation when appropriate (from #271). my app relies on
getPlatformProxy
so it cannot be deployed with any version of wrangler that doesn’t include that API. however, in my case, the logic to check that existing install and version if somehow falling through to the⚠️ Wrangler not found or version is incompatible. Installing...
fallback logic.here is my output from the workflow run, which shows that i am using yarn v1.22.22 and shows that
/usr/local/bin/yarn wrangler --version
, as invoked by wrangler-action, is returning the version number (3.63.2
) correctly:my hypothesis is that the issue is due to the fallback regex starting with the “start of string” token (
/^
):i’m not sure how
stdout
is derived, but if it includes anything before the version output (e.g.\n3.63.2
, or even/home/runner/work/outlyne/outlyne/node_modules/.bin/wrangler --version\n3.63.2
), the regex won’t match it.the most obvious solution, then, is to use multi-line mode so that
^
matches the start of every line as well as the start of the string:in case it’s helpful, this is my yaml from the workflow file itself:
The text was updated successfully, but these errors were encountered: