-
Notifications
You must be signed in to change notification settings - Fork 1.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
Enable cloudinary tests #5386
Enable cloudinary tests #5386
Conversation
🦋 Changeset detectedLatest commit: 9265dac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/HWqqfiq8Hutgt24szDaAJyWhfDUA |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9265dac:
|
d42c7d7
to
c07c3dd
Compare
e2f05ae
to
3ac5c36
Compare
3ac5c36
to
9b0b6a0
Compare
1a97b15
to
79f71bd
Compare
Re-enabling the cloudinary tests while we're doing some work on moving the cloudinary code around.
Update: I've made the changes required to make the tests all pass, but I'm going to leave them disabled, because we will completely chew through our API limits if they're enabled on all branches. We can now enable them on branches as needed when making changes around the cloudinary field type.