googleapis / googleapis/release-please-action

release branch name in v4

Open
#1,019 0 comments 0 reactions 0 assignees View on GitHub
priority: p3 type: question
Dominant language
TypeScript
Stars
2.5k
Forks
327
PR merge metrics
No merged PRs in 30d

Description

- What you're trying to do
In monorepo, i want to make various release branch

- What code you've already tried

### release-plase-config.json
```
{
"include-component-in-tag": true,
"tag-separator": "@",
"release-type": "simple",
"separate-pull-requests": true,
"changelog-sections": [{"type":"feat","section":"Features","hidden":false},{"type":"fix","section":"Bug Fixes","hidden":false},{"type":"chore","section":"Miscellaneous","hidden":false},{"type":"refactor","section":"Refactoring","hidden":false},{"type":"fix(deps)","section":"Dependency Update","hidden":false},{"type":"test","section":"Tests","hidden":false}],
"packages": {
"web/apps/service1": {
"package-name": "service1",
"component": "service1",
"include-component-in-tag": true,
"separate-pull-requests": true
}
}
}
```
### .release-please-mainfest.json

```
{
"web/apps/service1": "1.0.0"
}

```

### acitions.yml

```
name: Service1-ReleasePlease

on:
push:
branches:
- main
paths:
- "web/apps/service1/**"

permissions:
contents: write
pull-requests: write

jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v4
id: release
with:
token: ${{ secrets.GITHUB_TOKEN }}
path: "web/apps/service1"
release-type: simple
config-file: default
manifest-file: default
include-component-in-tag: 'true'
- name: deploy
if: ${{ steps.release.outputs['web/apps/service--release_created'] }}
run:
echo "deploy"
```

- Any error messages you're getting

스크린샷 2024-07-10 오후 2 25 15

release-please--branches--main is made but in comparing v3
release-please--branches--main--components--service is should made

Contributor guide

Open the contributing guide

Research direction

Start with the provided release-please-config.json, .release-please-mainfest.json, and GitHub Actions workflow, then compare v4's generated branch naming with the reported v3 behavior. Reproduce the monorepo configuration and verify that the release branch includes the service component, such as release-please--branches--main--components--service, rather than only release-please--branches--main.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.