release-please-config.json
Release Please manifest configuration file
| Type | object |
|---|---|
| File match |
release-please-config.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/release-please-config-json/latest.json |
| Source | https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json |
Validate with Lintel
npx @lintel/lintel check
Schema for defining manifest config file
Properties
All of
Definitions
The strategy to use for this component.
Breaking changes only bump semver minor if version < 1.0.0
Feature changes only bump semver patch if version < 1.0.0
Configuration option for the prerelease versioning strategy. If prerelease strategy used and type set, will set the prerelease part of the version to the provided value in case prerelease part is not present.
Versioning strategy. Defaults to default
Override the Changelog configuration sections
[DEPRECATED] Override the next version of this package. Consider using a Release-As commit instead.
Skip tagging GitHub releases for this package. Release-Please still requires releases to be tagged, so this option should only be used if you have existing infrastructure to tag these releases.Defaults to false.
Skip generating a changelog for this package. Defaults to false.
Create the GitHub release in draft mode. Defaults to false.
Force the creation of a Git tag for the release. This is particularly useful when draft is enabled, because GitHub does not create a Git tag for draft releases until they are published. This 'lazy tag creation' causes release-please to fail to find the previous release, potentially generating incorrect changelogs. Setting this to true ensures the tag is created immediately. Defaults to false.
Create the GitHub release as prerelease. Defaults to false.
Open the release pull request in draft mode. Defaults to false.
Comma-separated list of labels to add to a newly opened pull request
When tagging a release, include the component name as part of the tag. Defaults to true.
When tagging a release, include v in the tag. Defaults to true.
Include v in the GitHub release name. Defaults to true.
The type of changelog to use. Defaults to default.
Generate changelog links to this GitHub host. Useful for running against GitHub Enterprise.
Path to the file that tracks release note changes. Defaults to CHANGELOG.md.
Customize the release pull request title.
Customize the release pull request header.
Customize the release pull request footer.
Open a separate release pull request for each component. Defaults to false.
Always update the pull request with the latest changes. Defaults to false.
Customize the separator between the component and version in the GitHub tag.
Date format given as a strftime expression for the generic strategy.
Specify extra generic files to replace versions.
Path of commits to be excluded from parsing. If all files from commit belong to one of the paths it will be skipped
Path to the specialize version file. Used by ruby and simple strategies.
Label to add to snapshot pull request. Used by java strategies.
If set, do not propose snapshot pull requests. Used by java strategies.
Releases the initial library with a specified version
release-please automatically adds (space) in front of parsed ${component}. This option indicates whether that behaviour should be disabled. Defaults to false