Skip to content

Commit a5d8975

Browse files
vaindclaude
andcommitted
feat!: Change updater pr-strategy default to 'update'
BREAKING CHANGE: The default value for pr-strategy has been changed from 'create' to 'update'. Previously, the updater would create separate PRs for each dependency version. Now it maintains a single PR that gets updated with new versions. To preserve the previous behavior, explicitly set pr-strategy: create in your workflow configuration. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
1 parent 5f024a8 commit a5d8975

File tree

3 files changed

+16
-3
lines changed

3 files changed

+16
-3
lines changed

CHANGELOG.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,19 @@
44

55
### Breaking Changes
66

7+
Updater: The default value for `pr-strategy` has been changed from `create` to `update`.
8+
9+
This change means the updater will now maintain a single PR that gets updated with new dependency versions (instead of creating separate PRs for each version).
10+
11+
If you want to preserve the previous behavior of creating separate PRs, explicitly set `pr-strategy: create` in your workflow:
12+
13+
```yaml
14+
- uses: getsentry/github-workflows/updater@v3
15+
with:
16+
# ... other inputs ...
17+
pr-strategy: create # Add this to preserve previous behavior
18+
```
19+
720
Updater and Danger reusable workflows are now composite actions ([#114](https://github.com/getsentry/github-workflows/pull/114))
821
922
To update your existing Updater workflows:

updater/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,8 +129,8 @@ jobs:
129129
* default: Dependencies
130130
* `pr-strategy`: How to handle PRs.
131131
Can be either of the following:
132-
* `create` (default) - create a new PR for new dependency versions as they are released - maintainers may merge or close older PRs manually
133-
* `update` - keep a single PR that gets updated with new dependency versions until merged - only the latest version update is available at any time
132+
* `create` - create a new PR for new dependency versions as they are released - maintainers may merge or close older PRs manually
133+
* `update` (default) - keep a single PR that gets updated with new dependency versions until merged - only the latest version update is available at any time
134134
* `target-branch`: Branch to use as base for dependency updates. Defaults to repository default branch if not specified.
135135
* type: string
136136
* required: false

updater/action.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ inputs:
2828
pr-strategy:
2929
description: 'How to handle PRs - can be either "create" (create new PRs for each version) or "update" (keep single PR updated with latest version)'
3030
required: false
31-
default: 'create'
31+
default: 'update'
3232
target-branch:
3333
description: 'Branch to use as base for dependency updates. Defaults to repository default branch if not specified.'
3434
required: false

0 commit comments

Comments
 (0)