Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update to use latest Spring Boot version #10

Open
upgradingdave opened this issue May 31, 2022 · 1 comment
Open

Update to use latest Spring Boot version #10

upgradingdave opened this issue May 31, 2022 · 1 comment
Assignees
@upgradingdave
Labels
c7 c8 enhancement enhancement to existing feature high LOE I haven't done this before infra Infrastructure change enhancement maintenance things that must be done to keep the repo healthy needs testing test in a automated way to prevent regression

Comments

@upgradingdave
Copy link
Contributor

Looks like current code is using spring boot is 2.4.2, which was released Jan 2021.

Latest version is 2.6.6.

Might be worth to update to get latest features? Also probably a good item to discuss related to governance.
@plungu plungu added enhancement enhancement to existing feature infra Infrastructure change enhancement labels Jun 3, 2022
@plungu plungu added c7 c8 needs testing test in a automated way to prevent regression high LOE I haven't done this before labels Aug 2, 2022
@plungu plungu added the maintenance things that must be done to keep the repo healthy label Aug 23, 2022
@upgradingdave
Copy link
Contributor Author

camunda-demo-ui is using spring boot 2.7.3
camunda-demo-data is using spring boot 2.7.3
camunda-8-process-solution-template is using spring boot 2.7.3

I think this is safe to close?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@upgradingdave upgradingdave

Labels
c7 c8 enhancement enhancement to existing feature high LOE I haven't done this before infra Infrastructure change enhancement maintenance things that must be done to keep the repo healthy needs testing test in a automated way to prevent regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@plungu @upgradingdave