Bump mock-server.version from 5.11.2 to 5.13.1 in /java #182
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.
Bumps
mock-server.version
from 5.11.2 to 5.13.1.Updates
mockserver-client-java
from 5.11.2 to 5.13.1Changelog
Sourced from mockserver-client-java's changelog.
... (truncated)
Commits
39d1cc6
[maven-release-plugin] prepare release mockserver-5.13.15195c0a
attempting to fix release process with new no-dependencies artefacts by addin...6284d51
attempting to fix release process with new no-dependencies artefacts - againe495086
improved steps on cleanup after failed releasecdcba06
added steps on cleanup after failed release678304f
attempting to fix release process with new no-dependencies artefacts3eb24de
put back parallel running in build server because without it the java crashes...4fa8917
removed step from release processa29d239
removed parallel maven execution from build server build to simplify understa...98ca70f
try to resolve flaky test that is only flaky in build serverUpdates
mockserver-core
from 5.11.2 to 5.13.1Changelog
Sourced from mockserver-core's changelog.
... (truncated)
Commits
39d1cc6
[maven-release-plugin] prepare release mockserver-5.13.15195c0a
attempting to fix release process with new no-dependencies artefacts by addin...6284d51
attempting to fix release process with new no-dependencies artefacts - againe495086
improved steps on cleanup after failed releasecdcba06
added steps on cleanup after failed release678304f
attempting to fix release process with new no-dependencies artefacts3eb24de
put back parallel running in build server because without it the java crashes...4fa8917
removed step from release processa29d239
removed parallel maven execution from build server build to simplify understa...98ca70f
try to resolve flaky test that is only flaky in build serverUpdates
mockserver-maven-plugin
from 5.11.2 to 5.13.1Commits
6d4da04
[maven-release-plugin] prepare release mockserver-maven-plugin-5.13.1b87ddf5
upgraded to MockServer 5.13.1 - missed one dependencye4d9b8f
upgraded to MockServer 5.13.144f9316
switched back to jar-with-dependencies to ensure JDK logging library integrat...47d5200
fix: upgrade com.google.guava:guava from 31.0.1-jre to 31.1-jrecdbae73
fix: upgrade com.google.guava:guava from 31.0.1-jre to 31.1-jre370123b
fixed invalid pom.xml492d7fd
fixes #1244 #1201 renamed all packages and added artefact called mockserver-m...9c87a63
fix: upgrade com.google.guava:guava from 31.0.1-jre to 31.1-jre5d419d2
fix: upgrade com.google.guava:guava from 31.0.1-jre to 31.1-jreDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)