googleapis / googleapis/release-please
Create a staging PR and production PR
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 588
- Avg merge
- 12h 16m
- Merged PRs (30d)
- 7
Description
Hi,
I would like to setup a workflow to deploy my applications (monorepo) in staging and production with release-please.
What are the best practices?
I thought about :
1. create a release-please-config.staging with:
```
{
"prerelease-type": "beta",
"release-type": "node",
"versioning-strategy": "prerelease",
"versioning-type": "prerelease",
"versioning": "prerelease",
"prerelease": true,
"include-v-in-tag": true,
"last-release-sha": "767ce15708e433867bdff190abf422d9d7defbeb",
"initial-version": "0.61.0",
"include-component-in-tag": true,
}
```
2. create a staging workflow on each PR merged on main. -> Release please create a PR with new features and fixes
3. If I merge this PR, it: a) create a staging tag like v1.1.0-beta b) run the release-please-config.production workflow with the
following config:
```
{
"release-type": "node",
"include-v-in-tag": true,
"last-release-sha": "767ce15708e433867bdff190abf422d9d7defbeb",
"initial-version": "0.61.0",
"include-component-in-tag": true,
"pull-request-title-pattern": "chore: release Production ${version}",
}
```
Release-please create a new PR for me, with a new version v1.1.0. If I merge this PR, it creates a tag
But if I don"t merge the production PR, and I add some new bug fixes, a new staging PR is created v1.1.0-beta.1
Is it possible to create such a workflow?
I tried with 2 release-please-manifests, but I am not convinced of the way to do it
Contributor guide
Assessment
This issue has not been assessed yet.