You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did make a pull request for upgrading this repo.
But I am wondering, why not using dependapod or renovate for this ?
EDIT: I have tried both dependapod and renovate on another (forked) spring-guide and found that renovate is much better in grouping together the changes (initial,complete,gradle,maven) for each dependency.
That means: you get just one merge request for updating spring-boot from 3.1.0 to 3.1.4 that includes the 2 subdirs (initial and complete) and in there both build.gradle and pom.xml. All in one merge request. dependapod seems to make 4 merge request in that case which sucks.
Hi @bodote . Thanks for the comment and the PR! I merged the PR.
I agree there are more automated ways to keep our dependencies up to date. For this project I want to keep the effort manual so we can provide issues for first time contributors. We've found a large audience that would like to contribute to OSS but aren't sure how to navigate the process. We're using this issue (and others in the spring-guides org) largely for educational purposes. Depending on the interest we may look at using an automated workflow in the future.
I will close this issue as the PR is merged. There will likely be new opportunities to upgrade the Boot version in the future.
Update the guide to use the most recent Spring Boot version.
Files that require changes are:
The text was updated successfully, but these errors were encountered: