Skip to content
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

[Snyk] Upgrade aws-amplify-react from 3.1.7 to 3.1.9 #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andalpopsie
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade aws-amplify-react from 3.1.7 to 3.1.9.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 26 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2020-03-30.
Release notes
Package name: aws-amplify-react
  • 3.1.9 - 2020-03-30
  • 3.1.9-unstable.7 - 2020-03-30
  • 3.1.9-unstable.6 - 2020-03-27
  • 3.1.9-unstable.5 - 2020-03-27
  • 3.1.9-unstable.4 - 2020-03-27
  • 3.1.9-unstable.3 - 2020-03-27
  • 3.1.9-unstable.2 - 2020-03-26
  • 3.1.9-unstable.1 - 2020-03-26
  • 3.1.9-unstable.0 - 2020-03-26
  • 3.1.8 - 2020-03-25
  • 3.1.8-unstable.15 - 2020-03-24
  • 3.1.8-unstable.14 - 2020-03-19
  • 3.1.8-unstable.12 - 2020-03-18
  • 3.1.8-unstable.11 - 2020-03-17
  • 3.1.8-unstable.10 - 2020-03-16
  • 3.1.8-unstable.9 - 2020-03-13
  • 3.1.8-unstable.8 - 2020-03-13
  • 3.1.8-unstable.7 - 2020-03-05
  • 3.1.8-unstable.6 - 2020-03-04
  • 3.1.8-unstable.5 - 2020-03-04
  • 3.1.8-unstable.4 - 2020-03-03
  • 3.1.8-unstable.3 - 2020-02-28
  • 3.1.8-unstable.2 - 2020-02-28
  • 3.1.8-unstable.1 - 2020-02-28
  • 3.1.8-unstable.0 - 2020-02-28
  • 3.1.8-PR-5187.36 - 2020-03-27
  • 3.1.7 - 2020-02-28
from aws-amplify-react GitHub release notes
Commit messages
Package name: aws-amplify-react
  • a105664 chore(release): Publish [ci skip]
  • 30e4c29 Preparing release
  • 71044ae fix builds that were broken by new terser 4.6.8 version (#5233)
  • d630c34 Added clientMetadata to sendMFACode (#5145)
  • 23d8d41 Export UsernameAttributes enum (#5197)
  • a4f518b feat(@ aws-amplify/datastore): configurable sync pagination limit (#5181)
  • c9c020d feat(@ aws-amplify/datastore): Make DataStore available in aws-amplify… (#5202)
  • 1d0b8e1 fix(@ aws-amplify/datastore): Make save return a single model instead of array (#5199)
  • 05f1b54 Fix AuthClass document typos (#5066)
  • cb902b0 Return promise in signIn (#5021)
  • 4cf7b72 chore(release): Publish [ci skip]
  • 7494acc Preparing release
  • 07292b1 Update to crypto-js@^3.3.0 (#5172)
  • ab08e38 chore: remove datastore form RN integ tests (#5139)
  • b884ea2 feat(@ aws-amplify/datastore): Support non-@ model types in DataStore (#5128)
  • 0ddb6af fix(@ aws-amplify/datastore): Storage should be re-initialized after DataStore.clear() (#5083)
  • 97b3186 chore: Fix setup-dev script (#5035)
  • 49f8bfe fix(aws-amplify-react): Fix Federated icons when using React Bo… (#5073)
  • fbbe244 fix(@ aws-amplify/pubsub): Allow to add async custom headers (#4931)
  • 0f7b0fc Merge branch 'master' into patch-1
  • 28ff4c9 fix(@ aws-amplify/datastore) Adding socket disconnection detection (#5086)
  • 0e79eea Merge branch 'master' into patch-1
  • dae4824 Fix(@ aws-amplify/interactions) fixes 4750 to properly use the spread operator (#4806)
  • fdca554 fix(@ aws-amplify/datastore): Fix query and delete types (#5032)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants