-
Notifications
You must be signed in to change notification settings - Fork 0
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 org.springframework.boot:spring-boot-starter-parent from 2.7.8 to 3.1.3 #106
Bump org.springframework.boot:spring-boot-starter-parent from 2.7.8 to 3.1.3 #106
Conversation
Bumps [org.springframework.boot:spring-boot-starter-parent](https://github.com/spring-projects/spring-boot) from 2.7.8 to 3.1.3. - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.8...v3.1.3) --- updated-dependencies: - dependency-name: org.springframework.boot:spring-boot-starter-parent dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Assuming the auth error gets fixed for GH Actions, This PR introduced quite a few changes and bring it up to speed with the current standards along with updating to Spring boot 3. The following significant changes have been made:
Given that these may not be 1:1 changes, we should run the E2E test first before merging. |
e2e test did not pass wilth all other service being latest (seems to be issue with CEGA auth), but that could be that the rewrite in this branch changed a previous mechanism for the test to avoid CEGA NSS on upload). I will try to test also with my different setup (not using that additional mechanism, but the regular CEGA NSS auth):
|
The StackTrace above is from the proxy server log (not the e2e test code stack trace). When testing the service on the tryggve server, using regular EGA username/password and ELIXIR_AAI_TOKEN, and run the new e2e test in a docker container from the tryggve server, I get the same stack trace in PROXY_proxy logs... So there seems to be something not working for real. |
@dependabot rebase |
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
A newer version of org.springframework.boot:spring-boot-starter-parent exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Already done and merged in. |
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps org.springframework.boot:spring-boot-starter-parent from 2.7.8 to 3.1.3.
Release notes
Sourced from org.springframework.boot:spring-boot-starter-parent's releases.
... (truncated)
Commits
9edc772
Release v3.1.35981252
Merge branch '3.0.x' into 3.1.x75f1604
Merge branch '2.7.x' into 3.0.xa1cd7e7
Upgrade to Spring Batch 5.0.34e6de6c
Upgrade to RxJava3 3.1.799a5543
Upgrade to Netty 4.1.97.Finaldf85c81
Upgrade to Spring Batch 5.0.34c719c1
Upgrade to RxJava3 3.1.748e3eba
Upgrade to Netty 4.1.97.Final25897b2
Upgrade to Spring Batch 4.3.9Dependabot 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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@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)