googleapis/release-please

Features

• Patch-Level Commit Markers - Marks a commit with the fix type to indicate a patch-level bug fix in the codebase.
• Accumulating Release PRs - Creates and maintains a single pull request that accumulates release notes until merged.
• Commit Message Structuring - Formats commit messages with a required type, optional scope, optional breaking change indicator, a description, optional body, and optional footers.
• Breaking Change Indicators - Indicates API-breaking modifications with a footer or a symbol after the type to signal a major version bump.
• Conventional Commit Parsers - Automates semantic version bumps and changelog generation by parsing commit messages that follow the Conventional Commits specification.
• Minor Feature Commit Markers - Marks a commit with the feat type to indicate a minor-level new feature in the codebase.
• Commit Standards - Structures commit messages with standardized types and scopes to enable automated changelog and version management.
• Monorepo Internal Dependency Synchronizers - Synchronizes version references across local packages when one of their dependencies is released.
• Manifest-Based Version Trackers - Records and retrieves the last-released version for each package from a manifest file to determine next version.
• Release Changelog Generators - Generates changelogs automatically by parsing conventional commit messages.
• Release Proposal Pull Request Creators - Opens and maintains pull requests that propose version bumps and append release notes.
• Release Pull Request Generators - Creates and maintains a pull request that proposes version bumps and release notes, updating as new commits are merged.
• Release Tracking Pull Request Creators - Creates pull requests that track all merged changes and stay updated until merged, then tags the release.
• Independent Monorepo Release Configurators - Configures separate component names for each releasable artifact so each gets its own version tag and release.
• Monorepo Release Managers - Coordinates independent or linked version releases for multiple packages in a single repository using a manifest file.
• Multi-Component Release Configurators - Configures independently versioned components in a monorepo so each artifact gets its own release and tag.
• Monorepo Release Coordinators - Manages independent or linked version releases for multiple packages or components within a single repository.
• Workspace Dependency Synchronizers - Updates inter-package dependency references across Node.js, Cargo, or Maven workspaces after a release.
• Automated Version Incrementing - Automatically calculates and applies the next semantic version from commit types.
• Draft Release Creators - Creates git tags and GitHub releases from merged pull requests, optionally as drafts.
• Release Configuration Tools - Defines per-package release types, version bumps, changelog sections, and prerelease settings in a JSON config file.
• Monorepo Independent Release Configurators - Configures manifests to release several packages or components from the same repository independently.
• GitHub Release Automators - Generates GitHub releases with release notes and git tags from structured commit history.
• Release PR-Based Generators - Creates and maintains a pull request that proposes version bumps and release notes, then publishes a GitHub release upon merge.
• Pull Request Release Taggers - Automatically tags commits and creates GitHub releases when a release pull request is merged.
• Monorepo Manifest Managers - Tracks multiple releasable components in a single repository using a JSON manifest.
• Commit-Based Versioning Engines - Determines the next version number automatically from commit message types and breaking changes.
• Latest Version Identification - Reads the current version from a manifest file or infers it by scanning commits, releases, and tags.
• Monorepo Versioning - Keeps multiple components in a monorepo at the same version by updating all to the highest version when any is bumped.
• Independent Versioning Configurators - Configures manifests to release distinct packages from the same repository with independent versioning.
• Manifest-Based Version Trackers - Records and retrieves the last released version for each package in a manifest file.
• Version Manifest Trackers - Stores last released versions for each component in a JSON manifest file for monorepo support.
• Change Intent Communication - Conveys the nature of each code change to teammates and stakeholders through a standardized commit format.
• Section Mappings - Maps conventional commit types to custom headings and ordering in the generated changelog.
• Multi-Part Commit Messages - Extends the commit message with a multi-paragraph body and structured footers for extra details.
• Commit Scope Annotations - Attaches a parenthesized scope after the commit type to specify which part of the codebase a change affects.
• Multi-Footer Commit Parsers - Embeds multiple conventional commit footers in a single commit message for separate changelog entries.
• Release Simulation Modes - Simulates release actions and logs detailed output without making changes to the repository.
• Commit-Type Pipeline Triggers - Kicks off automated build and deployment pipelines based on the types of commits detected in the history.
• Release Manifest Initializers - Generates initial configuration and manifest files via CLI or manual setup to enable automated releases for monorepos.
• Plugin Extensibility - Allows pre-processing and post-processing of release strategies through a plugin-based architecture.
• Pre and Post Processing Hooks - Extends release strategies with pre and post processing hooks for custom configuration and candidate modification.
• Language-Aware Version Bumpers - Detects language-specific files and applies the correct version-bump strategy for each package manager.

स्टार हिस्ट्री