chore: fix release javadocs #373
Merged
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
lucasmcdonald3
approved these changes
Sep 19, 2024
josecorella
approved these changes
Sep 19, 2024
josecorella
pushed a commit
that referenced
this pull request
Oct 4, 2024
## [3.2.3](v3.2.2...v3.2.3) (2024-10-04) ### Fixes * catch CompletionException instead when instruction file is not found ([#379](#379)) ([dd61547](dd61547)) * handle S3 server encoding of non-US-ASCII object metadata ([#375](#375)) ([b907743](b907743)) * introduce S3-specific client configuration to top-level configuration ([#378](#378)) ([54fa0cb](54fa0cb)) ### Maintenance * fix release cfn and codebuild ([#380](#380)) ([2844498](2844498)) * fix release javadocs ([#373](#373)) ([8a69959](8a69959))
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.
Issue #, if available:
Description of changes:
This step failed during the latest release. I ran it locally and it seems the path which javadocs are built to has changed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: