docs: update hardcoded Javadoc versions to 'latest' alias #377
Conversation
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
1 participant
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.
Description
Several Javadoc links in the project documentation were pointing to a specific old version (20240325.1). This PR updates those links in [README.md] and [getting_started.md] to use the
/latest/alias.Why this is needed
Using the
/latest/alias ensures that developers clicking these links are always directed to the most current API documentation, preventing the documentation from becoming stale after future releases.GSoC Context
I'm a prospective GSoC student getting familiar with the OWASP Java HTML Sanitizer project. I wanted to start by improving the project's documentation infrastructure before diving into larger feature proposals.