You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This adds a new configuration option `include-v-in-release-name` that
controls whether the `v` prefix is included in GitHub release names.
Previously, the release name was hardcoded to always include the `v`
prefix (e.g., `v1.2.3`). This change allows users to opt out of the
`v` prefix by setting `include-v-in-release-name: false` in their
release-please config.
The default behavior is unchanged (`true`), maintaining backwards
compatibility.
Changes:
- Added `include-v-in-release-name` to config schema
- Added `includeVInReleaseName` to ReleaserConfig interface
- Updated BaseStrategy to use the new option when building release name
- Added serialization support in release-please-config updater
- Added tests for the new functionality
Example config:
```json
{
"include-v-in-tag": false,
"include-v-in-release-name": false,
"packages": {
".": {
"release-type": "node"
}
}
}
```
With the above config, releases would be named `1.2.3` instead of `v1.2.3`.
0 commit comments