MajorLinux
6592eb4fea
- Fixed 4 broken markdown links (bad relative paths in See Also sections) - Corrected n8n port binding to 127.0.0.1:5678 (matches actual deployment) - Updated SnapRAID article with actual majorhome paths (/majorRAID, disk1-3) - Converted 67 Obsidian wikilinks to relative markdown links or plain text - Added YAML frontmatter to 35 articles missing it entirely - Completed frontmatter on 8 articles with missing fields Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
57 lines
1.4 KiB
Markdown
57 lines
1.4 KiB
Markdown
---
|
|
title: "Gemini CLI: Manual Update Guide"
|
|
domain: troubleshooting
|
|
category: general
|
|
tags: [gemini, cli, npm, update, google]
|
|
status: published
|
|
created: 2026-04-02
|
|
updated: 2026-04-02
|
|
---
|
|
# 🛠️ Gemini CLI: Manual Update Guide
|
|
|
|
If the automatic update fails or you need to force a specific version of the Gemini CLI, use these steps.
|
|
|
|
## 🔴 Symptom: Automatic Update Failed
|
|
You may see an error message like:
|
|
`✕ Automatic update failed. Please try updating manually`
|
|
|
|
## 🟢 Manual Update Procedure
|
|
|
|
### 1. Verify Current Version
|
|
Check the version currently installed on your system:
|
|
```bash
|
|
gemini --version
|
|
```
|
|
|
|
### 2. Check Latest Version
|
|
Query the npm registry for the latest available version:
|
|
```bash
|
|
npm show @google/gemini-cli version
|
|
```
|
|
|
|
### 3. Perform Manual Update
|
|
Use `npm` with `sudo` to update the global package:
|
|
```bash
|
|
sudo npm install -g @google/gemini-cli@latest
|
|
```
|
|
|
|
### 4. Confirm Update
|
|
Verify that the new version is active:
|
|
```bash
|
|
gemini --version
|
|
```
|
|
|
|
## 🛠️ Troubleshooting Update Failures
|
|
|
|
### Permissions Issues
|
|
If you encounter `EACCES` errors without `sudo`, ensure your user has permissions or use `sudo` as shown above.
|
|
|
|
### Registry Connectivity
|
|
If `npm` cannot reach the registry, check your internet connection or any local firewall/proxy settings.
|
|
|
|
### Cache Issues
|
|
If the version doesn't update, try clearing the npm cache:
|
|
```bash
|
|
npm cache clean --force
|
|
```
|