Repository navigation
Remove self-compiled binary warning - #1521
Merged
Merged
Conversation
nickvanw
approved these changes
Nov 12, 2026
dgraham
approved these changes
Nov 12, 2026
joshmgross
enabled auto-merge
November 12, 2026 20:36
mdlayher
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This removes the warning added in #431 when running the CLI as a self-compiled binary
The original motivation was accidental usage:
I suspect it would be difficult to accidentally self-compile
pscaleand the warning becomes quite annoying for regular development. I do not believe we should require everyone to set an arbitraryPSCALE_DISABLE_DEV_WARNINGenvironment variable.If users want to self-compile
pscale, they can. If there are issues with that, we can simply tell them to update to the latest version.