manually trigger maven sync on javadoc.io post-release - #167
Merged
Conversation
Andrew Kent (realark)
force-pushed
the
ark/javadoc-io-fix
branch
2 times, most recently
from
August 20, 2026 05:02
5715c4c to
6a210d9
Compare
Andrew Kent (realark)
marked this pull request as ready for review
August 20, 2026 05:08
javadoc.io is no longer auto-ingesting doc jars, so we'll poke it after we release to trigger a maven sync
Andrew Kent (realark)
force-pushed
the
ark/javadoc-io-fix
branch
from
August 20, 2026 05:13
6a210d9 to
15f9301
Compare
Abhijeet Prasad (AbhiPrasad)
approved these changes
Aug 20, 2026
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.
javadoc.io is no longer auto-ingesting doc jars. But, lucky for us, there's an undocumented api we can use to manually trigger a sync post-release.