Conversation
josecorella
approved these changes
Apr 5, 2023
aws-crypto-tools-ci-bot
pushed a commit
that referenced
this pull request
Apr 5, 2023
### [2.0.1](v2.0.0...v2.0.1) (2023-04-05) ### Fixes * remove illegal javadoc syntax ([#147](#147)) ([412a02c](412a02c)) * remove illegal javadoc tags ([#148](#148)) ([d5682b9](d5682b9)) ### Maintenance * point release at correct internal staging domain, fix group id ([#149](#149)) ([f88e89d](f88e89d))
aws-crypto-tools-ci-bot
pushed a commit
that referenced
this pull request
Apr 5, 2023
## [3.0.0](v2.0.0...v3.0.0) (2023-04-05) ### ⚠ BREAKING CHANGES * prod release for S3 EC (#152) ### Features * prod release for S3 EC ([#152](#152)) ([d724eab](d724eab)) ### Fixes * Revert "Amazon S3 Encryption Client 2.0.1 Release -- $(date +%Y-%m-%d)" (#151) ([a62e455](a62e455)), closes [#151](#151) * remove illegal javadoc syntax ([#147](#147)) ([412a02c](412a02c)) * remove illegal javadoc tags ([#148](#148)) ([d5682b9](d5682b9)) ### Maintenance * add the developer guide to the README ([#150](#150)) ([b41a07b](b41a07b)) * point release at correct internal staging domain, fix group id ([#149](#149)) ([f88e89d](f88e89d))
aws-crypto-tools-ci-bot
pushed a commit
that referenced
this pull request
Apr 6, 2023
## [3.0.0](v2.0.0...v3.0.0) (2023-04-06) ### ⚠ BREAKING CHANGES * prod release for S3 EC (#152) ### Features * prod release for S3 EC ([#152](#152)) ([d724eab](d724eab)) ### Fixes * Revert "Amazon S3 Encryption Client 2.0.1 Release -- $(date +%Y-%m-%d)" (#151) ([a62e455](a62e455)), closes [#151](#151) * remove illegal javadoc syntax ([#147](#147)) ([412a02c](412a02c)) * remove illegal javadoc tags ([#148](#148)) ([d5682b9](d5682b9)) ### Maintenance * add the developer guide to the README ([#150](#150)) ([b41a07b](b41a07b)) * point release at correct internal staging domain, fix group id ([#149](#149)) ([f88e89d](f88e89d))
aws-crypto-tools-ci-bot
pushed a commit
that referenced
this pull request
Apr 6, 2023
## [3.0.0](v2.0.0...v3.0.0) (2023-04-06) ### ⚠ BREAKING CHANGES * prod release for S3 EC (#152) ### Features * prod release for S3 EC ([#152](#152)) ([d724eab](d724eab)) ### Fixes * Revert "Amazon S3 Encryption Client 2.0.1 Release -- $(date +%Y-%m-%d)" (#151) ([a62e455](a62e455)), closes [#151](#151) * remove illegal javadoc syntax ([#147](#147)) ([412a02c](412a02c)) * remove illegal javadoc tags ([#148](#148)) ([d5682b9](d5682b9)) ### Maintenance * add scm url to pom.xml ([#155](#155)) ([22ac9ad](22ac9ad)) * add the developer guide to the README ([#150](#150)) ([b41a07b](b41a07b)) * point release at correct internal staging domain, fix group id ([#149](#149)) ([f88e89d](f88e89d))
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.
Issue #, if available:
Description of changes:
Removes illegally used
</p>tags. They're allowed elsewhere but are apparently illegal in their former usage.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: