-
Notifications
You must be signed in to change notification settings - Fork 125
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
Bump svnkit-cli from 1.10.10 to 1.10.11 #238
base: master
Are you sure you want to change the base?
Bump svnkit-cli from 1.10.10 to 1.10.11 #238
Conversation
7ae4555
to
4120d4b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not yet in subversion
plugin.
4120d4b
to
309c3c4
Compare
@dependabot rebase |
Bumps svnkit-cli from 1.10.10 to 1.10.11. --- updated-dependencies: - dependency-name: org.tmatesoft.svnkit:svnkit-cli dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
309c3c4
to
2e47ccf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This SVNKit update is still not included in subversion
, but tests pass anyway. Also https://subversion.apache.org/news.html#news-20230924 says 1.10.x is EOL (CC @didiez) though https://svnkit.com/download.php shows 1.10.10 as the latest and https://svn.svnkit.com/repos/svnkit/tags/ shows 1.10.11.
Not sure if it still worth even including SVN-specific integration tests in Pipeline plugins. The plugin is widely installed, but that is due to its “split” status; based on metrics from @cloudbees customers, it is essentially never used. Not sure if @jenkinsci collects analogous information.
compare jenkinsci/subversion-plugin#288 |
Bumps svnkit-cli from 1.10.10 to 1.10.11.
You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)