create-github-app-token/release-please-config.beta.json at main - create-github-app-token - Gitea: Git with a cup of tea

actions/create-github-app-token

Files

T

Parker Brown 6dbbbb1419 ci: use existing release tag format (#369 )

## Summary

This updates the release-please manifest configuration to use the
repository's existing `vX.Y.Z` tag format. Without this setting,
manifest mode looks for component-prefixed tags like
`create-github-app-token-v3.1.1`, which do not exist in this repository
and can cause release-please to include already-released commits in a
new release PR.

## Changes

- Sets `include-component-in-tag` to `false` for stable releases.
- Sets `include-component-in-tag` to `false` for beta prereleases.

This should make release-please use tags like `v3.1.1` as the previous
release boundary.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-05-07 18:58:55 -07:00

13 lines

305 B

JSON

Raw Permalink Blame History

 {
   "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
   "packages": {
     ".": {
       "prerelease": true,
       "prerelease-type": "beta",
       "include-component-in-tag": false,
       "release-type": "node",
       "versioning": "prerelease"
     }
   }
 }