Support Center/Reading the Changelog

Reading the Changelog

Learn how to use the Helm changelog to stay informed about releases, features, bug fixes, and breaking changes.

Reading the Changelog

The Helm changelog keeps you informed about all releases, features, bug fixes, and important updates to the platform. This article explains how to navigate and understand the changelog.

Accessing the Changelog

Visit /changelog to view the complete release history. The changelog is publicly accessible and does not require authentication.

Understanding Entry Types

Each changelog entry is categorized by type:

  • Release: Major or minor version releases with multiple features and improvements
  • Feature: New capabilities added to Helm
  • Update: Enhancements and improvements to existing functionality
  • Fix: Bug fixes and patches
  • Breaking Change: Changes that may require action on your part

Entry Information

Each changelog entry includes:

  • Title: A descriptive name for the release or update
  • Date: When the change was published
  • Version: The semantic version number (e.g., v1.2.0)
  • Type Badge: Visual indicator of the entry type
  • Description: Summary of what changed
  • GitHub Link: Link to the full release notes on GitHub
  • Data Source

    The changelog is automatically populated from the Helm GitHub repository releases. This ensures that release information is always accurate and up-to-date.

    If GitHub is temporarily unavailable, the changelog will display cached data with a notice indicating the data source.

    Pre-release Versions

    Pre-release versions (alpha, beta, release candidates) may appear in the changelog with a "Pre-release" badge. These versions are for testing purposes and may not be suitable for production use.

    Staying Informed

    To stay up-to-date with Helm releases:

  • Visit the changelog regularly
  • Star or watch the Helm GitHub repository for notifications
  • Subscribe to release notifications in your GitHub settings
  • Related Topics