-
Notifications
You must be signed in to change notification settings - Fork 53
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
Bugfix/fix deprecated packages #276
Bugfix/fix deprecated packages #276
Conversation
Thanks for this contribution! It looks good to me. I need to figure out a way to get the CI build working w/out need to access the context object. Worst case, I'll try to manually validate the build later this week. |
@lostunicorn Would you mind pulling/merging the latest changes from |
Thanks. Looks like the CI build succeeded, but the
|
@bhamail I can't reproduce the error on my machine yarn run test-ci works
and yarn run test works
Is it possible there's a circleci issue that prevents writing to |
@lostunicorn I ran your branch locally, and the tests are fine there too, so I'm gonna merge this puppy and we'll deal with any surprises on 'main' if they occur. Fingers crossed. ;) |
🎉 This PR is included in version 4.0.44 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Thx @bhamail 🙂 |
Update dependencies to fix a number of vulnerabilities reported by npm audit + use non-deprecated packages
This pull request makes the following changes:
Was on the fence about regenerating the entire yarn.lock file, but decided in favor of incremental changes
It relates to the following issue #s:
cc @bhamail / @DarthHater / @allenhsieh / @ken-duck