Docs: Clarify "stable" vs. "latest" installation versions and update CHANGELOG

Resolved 💬 4 comments Opened Aug 14, 2025 by coygeek Closed Jan 4, 2026

Title: Docs: Clarify "stable" vs. "latest" installation versions and update CHANGELOG

Labels: documentation, bug

Problem Description

The installation documentation in en/docs/claude-code/setup provides options for installing a "stable" version and a "latest" version using the install.sh script. However, there is conflicting information across official sources, making it unclear what these versions refer to and what the difference is between them.

Points of Confusion
  1. Installation Documentation: The docs provide the following commands, implying a difference between the two versions:

```bash
# Install stable version (default)
curl -fsSL https://claude.ai/install.sh | bash

# Install latest version
curl -fsSL https://claude.ai/install.sh | bash -s latest
```

  1. NPM vs. CHANGELOG: There is a discrepancy between the version listed on NPM and the version in the GitHub CHANGELOG.
  • NPM Page: Shows the latest published version is 1.0.80.
  • GitHub CHANGELOG.md: The latest version listed is 1.0.73.
  1. Local Installation: Running claude --version after a fresh installation confirms the version is 1.0.80.

This leads to the core question: What is the intended difference between the "stable" and "latest" install options?

Currently, both options appear to install the same version (1.0.80), which makes the distinction in the documentation confusing for users trying to make an informed choice. Furthermore, the outdated CHANGELOG.md makes it difficult to track changes between versions.

Suggested Improvements

To resolve this ambiguity and improve the user experience, we suggest the following:

  1. Update the CHANGELOG.md: Please ensure the changelog on GitHub is kept in sync with the versions published to NPM. This is a critical resource for users to understand what's new.
  2. Clarify the Documentation: In en/docs/claude-code/setup, please clarify the release strategy.
  • If stable and latest are currently identical, the documentation should state that.
  • If they are intended to be different (e.g., stable is a less-frequent, vetted release and latest is the most recent feature release), please define that distinction clearly.
  • Ideally, provide the actual version numbers for the current stable and latest releases directly in the docs for maximum clarity.

Thank you for creating such a powerful tool! A little more clarity on the versioning and release process would be very helpful.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗