Skip to content

Conversation

@tannerlinsley
Copy link
Member

No description provided.

@netlify
Copy link

netlify bot commented Jan 16, 2026

Deploy Preview for tanstack ready!

Name Link
🔨 Latest commit f5db0e3
🔍 Latest deploy log https://app.netlify.com/projects/tanstack/deploys/696acf8bc3364d000804225a
😎 Deploy Preview https://deploy-preview-668--tanstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 18
Accessibility: 90
Best Practices: 75
SEO: 97
PWA: 70
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@tannerlinsley tannerlinsley merged commit 40a260d into main Jan 16, 2026
0 of 3 checks passed
@tannerlinsley tannerlinsley deleted the blog-restructure branch January 16, 2026 23:53
@gitguardian
Copy link

gitguardian bot commented Jan 16, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
10208042 Triggered Generic High Entropy Secret f5db0e3 docs/mcp/config.json View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. 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


🦉 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.

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.

3 participants