Bump io.rest-assured:rest-assured from 5.3.1 to 5.3.2 #360
Conversation
This file contains 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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [io.rest-assured:rest-assured](https://github.com/rest-assured/rest-assured) from 5.3.1 to 5.3.2. - [Changelog](https://github.com/rest-assured/rest-assured/blob/master/changelog.txt) - [Commits](https://github.com/rest-assured/rest-assured/commits) --- updated-dependencies: - dependency-name: io.rest-assured:rest-assured dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
MarkEWaite
added a commit
to MarkEWaite/github-plugin
that referenced
this pull request
Oct 10, 2023
Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21. The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21. The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code. Also updates parent pom to most current release and removes unneeded hamcrest dependency declaration. Supersedes pull request: * jenkinsci#367 * jenkinsci#366 * jenkinsci#361 * jenkinsci#360 * jenkinsci#359 * jenkinsci#353 * jenkinsci#352
MarkEWaite
added a commit
to MarkEWaite/github-plugin
that referenced
this pull request
Oct 10, 2023
Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21. The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21. The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code. Also updates parent pom to most current release and removes unneeded hamcrest dependency declaration. Supersedes pull request: * jenkinsci#367 * jenkinsci#366 * jenkinsci#361 * jenkinsci#360 * jenkinsci#359 * jenkinsci#353 * jenkinsci#352
oleg-nenashev
pushed a commit
that referenced
this pull request
Nov 12, 2023
* Test with Java 21 Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21. The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21. The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code. Also updates parent pom to most current release and removes unneeded hamcrest dependency declaration. Supersedes pull request: * #367 * #366 * #361 * #360 * #359 * #353 * #352 * Test Java 11 directly Address the concern that Oleg expressed in #368 (review) We've detected no regressions with the transition to testing Java 11 byte code as generated by Java 17 and Java 21 compilers in the 200+ plugins that have made the transition. We test with Java 11 on older lines (Jenkins 2.401.x and Jenkins 2.414.x) in the plugin bill of materials while testing with Java 21 on the most recent weekly release. We've detected no issues with any of the plugins that are included in the plugin BOM. We want to reduce Jenkins infrastructure costs by not testing configurations that are unlikely to detect issues. Testing with Java 11 is unlikely to detect issues and adds infrastructure cost. I've added Java 11 on Linux as a test configuration. I do not intend to make that same addition on the other 100+ repositories where we're testing with Java 21 and Java 17. When a plugin maintainer asks to continue testing Java 11, I'm willing to adapt that pull request. * Revert "Test Java 11 directly" This reverts commit 6d8ef2f.
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.
Bumps io.rest-assured:rest-assured from 5.3.1 to 5.3.2.
Changelog
Sourced from io.rest-assured:rest-assured's changelog.
Commits
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)