Upgrade library versions in Java tutorials#424
Merged
tomwheeler merged 6 commits intomainfrom Nov 5, 2025
Merged
Conversation
…estamps, clarified explanations of libraries, and removed unnecessary version numbers from prose)
…at is in the code above (and thus increase the burden of keeping them updated and in sync)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tomwheeler
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What was changed
I updated the version numbers for the Temporal SDK and all project dependencies (junit, slf4j, commons-lang, etc.) to the latest stable versions.
Why?
As @LightGuard rightly points out in #383, the Temporal SDK referenced in these tutorials was several versions behind what's current, as were other libraries used in those tutorials. I updated them to what is now the latest stable release. This eliminates security vulnerabilities in older versions of project dependencies (such as JUnit or Apache Commons Lang) and also conveys to our learners that these tutorials are maintained and worth their time to complete.
Checklist
#383
Most of these changes were to prose, for which there is no automated test. After I submit this PR, I will update the corresponding code in each of the tutorial repos and run the automated tests to validate that they work as expected in the new versions (however, I do not expect any problems because these are all minor upgrades, which should maintain compatibility with the earlier versions). There were two complete projects in this repository, both related to the Java version of the background check application, which had
pom.xmlfiles and I tested that by runningmvn clean test(both executions were successful).This is the doc update, but no further updates are needed.