-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Setup v5 LTS CI infrastructure #12455
Merged
Merged
+79
−1
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
- amazon-cognito-identity-js@6.3.7 - @aws-amplify/api-graphql@3.4.12 - @aws-amplify/api@5.4.6 - @aws-amplify/auth@5.6.6 - aws-amplify@5.3.12 - @aws-amplify/datastore-storage-adapter@2.0.49 - @aws-amplify/datastore@4.7.6 - @aws-amplify/notifications@1.6.6 - @aws-amplify/pubsub@5.5.6 - @aws-amplify/rtn-push-notification@1.1.8
- @aws-amplify/analytics@6.5.6 - @aws-amplify/api-graphql@3.4.13 - @aws-amplify/api-rest@3.5.6 - @aws-amplify/api@5.4.7 - @aws-amplify/auth@5.6.7 - aws-amplify@5.3.13 - @aws-amplify/cache@5.1.12 - @aws-amplify/core@5.8.6 - @aws-amplify/datastore-storage-adapter@2.0.50 - @aws-amplify/datastore@4.7.7 - @aws-amplify/geo@2.3.6 - @aws-amplify/interactions@5.2.12 - @aws-amplify/notifications@1.6.7 - @aws-amplify/predictions@5.5.6 - @aws-amplify/pubsub@5.5.7 - @aws-amplify/pushnotification@5.0.46 - @aws-amplify/storage@5.9.6
This reverts commit 8e210b1.
This reverts commit 194cc3b.
This reverts commit 0acc70e.
elorzafe
approved these changes
Oct 27, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Thanks @jimblanc
stocaaro
approved these changes
Oct 27, 2023
jimblanc
added a commit
to jimblanc/amplify-js
that referenced
this pull request
Oct 27, 2023
4 tasks
jimblanc
added a commit
that referenced
this pull request
Oct 30, 2023
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.
Description of changes
This change sets up new CI infrastructure to release v5 LTS changes.
Changes will be released to a
stable-5
dist tag in NPM (latest won't be updated).Differences from "current major version" releases:
required-release
tag will be generated at this timerelease
branch just for LTS versions)Issue #, if available
Description of how you validated changes
Tested
v5-stable
deployment target in Verdaccio and confirmedlatest
was unimpacted. Tested Github workflows & actions against my fork.Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.