feat: CodeArtifact Migration - Phase 1 & Phase 2 #142
Merged
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
svanherk
requested review from
dlockhart,
dbatiste and
njostonehouse
as code owners
svanherk
commented
May 30, 2022
| @@ -4,7 +4,6 @@ | |||
| <meta charset="utf-8"> | |||
There was a problem hiding this comment.
I left this file the messy Polymer demo style so we can test the old Polymer mixins with messy Polymer style things
|
I also deleted all the old screenshots that are no longer referenced by the README and may not be accurate |
dlockhart
approved these changes
May 30, 2022
|
🎉 This PR is included in version 8.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
ghost
added
the
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.
This PR updates all the ci tech (Travis -> GitHub Actions, update linting, add semantic-release) and does Phase 1 and 2 of the CodeArtifact migration.
Phase 1:
publishConfigandfilestopackage.jsonrelease.ymlworkflow accordingly (will vary depending on release action used)Releasessection to mention it publishes tonpmPhase 2:
Phase 2 only has this one step because it doesn't pull in any other repos we're updating.