Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block automerge itself for semver major #110

Closed
2 tasks done
Eomm opened this issue Nov 26, 2021 · 0 comments · Fixed by #114
Closed
2 tasks done

Block automerge itself for semver major #110

Eomm opened this issue Nov 26, 2021 · 0 comments · Fixed by #114
Assignees

Comments

@Eomm
Copy link
Member

Eomm commented Nov 26, 2021

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure the issue has not already been raised

Issue

Refs:

When we release a major version of this GHA, dependabot will open a PR against this GHA users.
The github-action-merge-dependabot will merge the PR updating itself assuming users has the default target: any configuration.

This must not happen: a major bump of this GHA must be done manually by the user because a major release (could) mean a new GHA syntax.

The github-action-merge-dependabot cannot upgrade itself regardless the target filter.

In this case, we should:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant