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

Make github compare link in bun upgrade --canary use the git sha of the new build instead of main #4115

Closed
leeoniya opened this issue Aug 11, 2023 · 4 comments · Fixed by #16432
Labels
cli Something to do with CLI arguments enhancement New feature or request

Comments

@leeoniya
Copy link

What platform is your computer?

Linux 6.1.4-arch1-1 x86_64 unknown

How did you attempt to install or upgrade?

image

What do you see instead?

one hash is from 30min ago, the other is from 3 days ago. they can't both be correct?

Additional information

No response

@leeoniya leeoniya added the bug Something isn't working label Aug 11, 2023
@Jarred-Sumner
Copy link
Collaborator

The previous hash is the one you were on before. The 2nd hash is the one you're on now.

@leeoniya
Copy link
Author

leeoniya commented Aug 11, 2023

but it won't always be main then since it needs to wait for CI? so main should actually be the revision hash?

can the compare url use shortened hashes, too?

@Jarred-Sumner
Copy link
Collaborator

Jarred-Sumner commented Aug 11, 2023 via email

@Jarred-Sumner Jarred-Sumner changed the title which bun version hash should i believe? Make github compare link in bun upgrade --canary use the git sha of the new build instead of main Aug 11, 2023
@Jarred-Sumner Jarred-Sumner added enhancement New feature or request and removed bug Something isn't working labels Aug 11, 2023
@birkskyum
Copy link
Collaborator

birkskyum commented Aug 11, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Something to do with CLI arguments enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants