We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Gradle
7.6
Java
It's a public repo, here are the most recent invalid PRs opened with all details:
We configure multiple branches in the depedabot.yml from the main branch.
depedabot.yml
https://github.com/spring-cloud/spring-cloud-app-broker/blob/d9535220afc5e07af61ff5237033d42d8efb9cd1/.github/dependabot.yml#L1
We see minor bumps when these should not me allowed.
ignore: - dependency-name: "org.springframework.boot:*" update-types: - "version-update:semver-major" - "version-update:semver-minor" - dependency-name: "spring-cloud-starter-op
In the case of the spring-cloud/spring-cloud-app-broker#818, a 3.0.9 exists that does not get a PR, instead we get 3.1.2 bump.
Does not apply.
Here are the most recent invalid PRs opened:
Truth be told, we have similar policies in other repos and we've only seen a repeated error in this repo/branch.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
Package ecosystem
Gradle
Package manager version
7.6
Language version
Java
Manifest location and content before the Dependabot update
It's a public repo, here are the most recent invalid PRs opened with all details:
dependabot.yml content
We configure multiple branches in the
depedabot.yml
from the main branch.https://github.com/spring-cloud/spring-cloud-app-broker/blob/d9535220afc5e07af61ff5237033d42d8efb9cd1/.github/dependabot.yml#L1
Updated dependency
We see minor bumps when these should not me allowed.
What you expected to see, versus what you actually saw
In the case of the spring-cloud/spring-cloud-app-broker#818, a 3.0.9 exists that does not get a PR, instead we get 3.1.2 bump.
Native package manager behavior
Does not apply.
Images of the diff or a link to the PR, issue, or logs
Here are the most recent invalid PRs opened:
Smallest manifest that reproduces the issue
Truth be told, we have similar policies in other repos and we've only seen a repeated error in this repo/branch.
The text was updated successfully, but these errors were encountered: