Merged
Conversation
jglick
commented
Jan 4, 2023
.github/dependabot.yml
Outdated
Comment on lines
+5
to
+12
| - package-ecosystem: maven | ||
| directory: / | ||
| schedule: | ||
| interval: monthly | ||
| - package-ecosystem: github-actions | ||
| directory: / | ||
| schedule: | ||
| interval: monthly |
Member
Author
There was a problem hiding this comment.
Was not previously enabled; will produce a steady flow of PRs, though they can be ignored if you prefer. (Note that updating the POM would require a switch to 2.361.x and Java 11.)
| </license> | ||
| </licenses> | ||
|
|
||
| <developers> |
Member
Author
There was a problem hiding this comment.
All obsolete, not helpful.
timja
approved these changes
Mar 25, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Possible as of jenkins-infra/repository-permissions-updater#3057. See: https://www.jenkins.io/doc/developer/publishing/releasing-cd/ and in particular the description of the version number format change.
@didiez this is just up to you; do not hesitate to close if you prefer to
mvn release:{prepare,perform}manually with the existing version scheme. If this is merged, then it becomes possible to cut releases merely by merging appropriately-labeled PRs. (All PRs should be given one of the stock labels likedependencies,chore,enhancement, orbugbefore merge.)