-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
gemini-cli-bin: init at 0.2.2 #432759
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
base: master
Are you sure you want to change the base?
gemini-cli-bin: init at 0.2.2 #432759
Conversation
4bb52d2
to
5af013a
Compare
|
5af013a
to
85fa47d
Compare
85fa47d
to
e72346d
Compare
e72346d
to
474e713
Compare
|
474e713
to
83a988a
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved automatically following the successful run of nixpkgs-review
.
Nice idea, lgtm |
83a988a
to
8ad68a1
Compare
8ad68a1
to
0c3007d
Compare
0c3007d
to
f3a9506
Compare
f3a9506
to
78231b9
Compare
Added |
Add a "binary" variant of
gemini-cli
using thegemini.js
release asset from upstream.This provides a much smaller package size and makes updates easier, as we won't have to worry about upstream build changes or missing dependencies.
Known Issue:
Running the
gemini
command from this package will print aDeprecationWarning
from Node.js, as shown below.This is because the upstream
gemini.js
build still depends on Node.js's deprecatedpunycode
module. The warning won't affect any functionality ofgemini-cli
and is expected to be suppressed after the Node.js v22.17.0 update.Things done
passthru.tests
.nixpkgs-review
on this PR. See nixpkgs-review usage../result/bin/
.Add a 👍 reaction to pull requests you find important.