Skip to content

Commit 3d2cf64

Browse files
committed
fix(release): use stable versioning instead of prerelease
Both SDKs are at a stable 1.30.0, but the scaffolded release-please-config.json still carried the prerelease strategy, which would cut 1.31.0-alpha.1 on the first stock release-please run. versioning: prerelease -> default (the field that adds the -alpha.N suffix) prerelease: true -> false (marks the GitHub Release as a prerelease) Both values verified against googleapis/release-please's published config schema: versioning "defaults to `default`", prerelease is "create the GitHub release as prerelease". Hand-edited rather than configured: publish.release.prerelease: false in stainless.yml does not reach this file. stlc scaffolds it once and preserves it thereafter, and --rewrite-scaffold does not refresh it — with the file deleted and --rewrite-scaffold passed, stlc did not recreate it at all. Preserved scaffold is the documented place for hand-edits to survive.
1 parent 14f64c6 commit 3d2cf64

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

release-please-config.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55
"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
66
"include-v-in-tag": true,
77
"include-component-in-tag": false,
8-
"versioning": "prerelease",
9-
"prerelease": true,
8+
"versioning": "default",
9+
"prerelease": false,
1010
"bump-minor-pre-major": true,
1111
"bump-patch-for-minor-pre-major": false,
1212
"pull-request-header": "Automated Release PR",

0 commit comments

Comments
 (0)