chore(release/proxy-sigv4-backend): publish v0.3.0 #13
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
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.
Generating CHANGELOG and preparing a new version release for the
proxy-sigv4-backendpackage.Following #5 as prior art, but some changes will need to take place going forward.
Since the original released include
--no-git-tag-version, we lose CHANGELOG history tracking, so every CHANGELOG is generated with all commits. I manually modified this version so that we can have a proper CHANGELOG history.We'll need to resolve what tagging looks like on releases for this plugin so that we don't duplicate things in the CHANGELOG moving forward.
Once this is merged, then I will run the
npx lerna publish from-package --no-verify-accesscommand to officially publish the new version.