-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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(docs): bump docusaurus dependencies #4168
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/DLwYpJvt8TAZPGNWFJPvHSAJMLe8 |
Had to do a few dummy commits to get Vercel to not cancel the deployment and double check algolia was still working 😅 All good though, ready to merge imo 👍 |
Looks like there are conflicts, otherwise LGTM |
* chore: simplify example-gatsby readme header * chore(docs): upgrade docusaurus deps * chore: dummy commit - will revert * chore: revert dummy commit * chore: revert rm searchParameters option * chore: more dummy update 🤦 * chore(docs): new aloglia apiKey * chore(docs): revert dummy update
Reasoning 💡
Updated
docusaurus
dependency's to their latest version. Thebeta.16
was a relatively big release on their part.3.0.0
stable, which matches up with the new "AlgoliaCrawler" product we're using on their end (deets)Aloglia update required new
appId
andapiKey
. These are both public so no worries 👍I didn't realize until reading these migration docs now, but old indexes not migrated to these new keys have been frozen and read-only since Feb 1 apparently.
Checklist 🧢
Affected issues 🎟