-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Canary Dockerfile bun build --compile is weird #16942
Comments
So the modern commit hash is the release of Note there is only "one" canary release that gets replaced, so even if this was fixed to pull latest canary it has chance of desyncing still. |
Makes sense now, it installs the other binaries through npm. Not sure best way to use same canary though (there is a nightly canary publish on npm so maybe). Lines 72 to 97 in fa50250
|
What version of Bun is running?
1.2.1-canary.37+d4ce42198
What platform is your computer?
No response
What steps can reproduce the bug?
What is the expected behavior?
Every build uses the same revision, or at least a relatively new one. Baseline matches the docker iamges I'm running, but modern is very old.
Canary is not that useful for testing if it's not up to date, and weird for testing if the results are not predictable.
The text was updated successfully, but these errors were encountered: