-
Notifications
You must be signed in to change notification settings - Fork 921
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
[@builder.io/gatsby] update to gatsby 4 and use graphql-source to fetch data for batching and retries #762
Conversation
Ideally this plugin is built using the gatsy-source-graphql as in this commit cd5da83 , unfortunately this is blocked by this issue gatsbyjs/gatsby#34042 so opt it to make a temporary fork until the pr with the fix is merged |
* 'main' of github.com:BuilderIO/builder: (194 commits) chore(core-sdk): publish 1.1.26 chore(deps): bump nanoid from 3.1.25 to 3.3.1 in /examples/vue/nuxt-2 chore(deps): bump node-fetch from 2.6.1 to 2.6.7 in /examples/vue/nuxt-2 chore(deps): bump node-fetch in /examples/vue/vue-storefront-2 chore(deps): bump cached-path-relative in /examples/vue/vue-storefront-2 chore(deps): bump nanoid in /examples/vue/vue-storefront-2 fix(sdk): respect this.canTrack for cookie fix(sdk): respect this.canTrack for cookie example(vue): setup nuxt-2 example on old vue SDK chore(examples): move all Vue examples under vue/ fix: contentful plugin undefined locate chore(deps): bump postcss in /examples/gatsby-minimal-starter chore(deps): bump postcss from 7.0.26 to 7.0.39 in /examples/storybook chore(deps): bump postcss from 7.0.35 to 7.0.39 in /examples/vue-nuxt chore(deps): bump postcss from 7.0.35 to 7.0.39 in /packages/gatsby chore(deps): bump postcss from 7.0.27 to 7.0.39 in /packages/storybook chore(deps): bump vm2 in /starters/create-builder/nextjs chore(deps): bump follow-redirects chore(deps): bump vm2 in /starters/create-builder/create-react-app chore(deps): bump ajv from 6.12.0 to 6.12.6 in /packages/codegen ...
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Generic High Entropy Secret | b29b326 | examples/react-native/App.tsx | View secret |
- | Generic High Entropy Secret | b29b326 | examples/vue/nuxt-2-old-sdk/pages/_page.vue | View secret |
- | Generic High Entropy Secret | b29b326 | examples/vue/nuxt-2/pages/_page.vue | View secret |
- | Generic High Entropy Secret | b29b326 | examples/vue/nuxt-2/pages/_page.vue | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
No description provided.