Bump Doxia to v1.11.1 & maven-site-plugin IT to v3.12.0 #579
Conversation
This file contains 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
abelsromero
force-pushed
the
bump-doxia-and-maven-site-plugin-versions
branch
from
c4907db
to
c549404
Compare
abelsromero
force-pushed
the
bump-doxia-and-maven-site-plugin-versions
branch
from
c549404
to
0316df1
Compare
abelsromero
added a commit
that referenced
this pull request
Mar 15, 2023
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Maintenance chore, bumping site related dependencies to most up to date compatible versions (docs included.)
Also tested maven-site-plugin v3.11.0 locally to make sure all versions between 3.10 and 3.12 are fine.
Are there any alternative ways to implement this?
N/A
Are there any implications of this pull request? Anything a user must know?
No big change, just maintenance
Is it related to an existing issue?
Not closing, but inspired by #578
Finally, please add a corresponding entry to CHANGELOG.adoc