Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update checker says new canary is available after upgrading to most recent canary #16539

Closed
GJZwiers opened this issue Nov 4, 2022 · 1 comment · Fixed by #16542
Closed
Labels
duplicate a duplicate of another issue

Comments

@GJZwiers
Copy link
Contributor

GJZwiers commented Nov 4, 2022

Basically I ran deno upgrade --canary and then deno run --unstable someFile.ts shortly after. Deno then notifies about a new canary being available, even though I am on the latest version already.

deno upgrade --canary

Looking up latest canary version
Found latest version 1410e4adea5d399f9551ff04c6863862f169ee7a
Checking https://dl.deno.land/canary/1410e4adea5d399f9551ff04c6863862f169ee7a/deno-x86_64-unknown-linux-gnu.zip
36.1 MiB / 36.1 MiB (100.0%)
Deno is upgrading to version 1410e4adea5d399f9551ff04c6863862f169ee7a
Archive:  /tmp/.tmpJJ01pQ/deno.zip
  inflating: deno                    
Upgraded successfully

deno run --unstable someFile.ts

A new canary release of Deno is available. Run `deno upgrade --canary` to install it.

deno --version
deno 1.27.1+1410e4a (canary, x86_64-unknown-linux-gnu)
v8 10.8.168.4
typescript 4.8.3

deno upgrade --canary
Looking up latest canary version
Local deno version 1.27.1+1410e4a is the most recent release
@dsherret
Copy link
Member

dsherret commented Nov 5, 2022

Duplicate of #16537

@dsherret dsherret marked this as a duplicate of #16537 Nov 5, 2022
@dsherret dsherret closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate a duplicate of another issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants