Infrastructure/view transitions optimization - #466
Conversation
…ad hoc regex for valid UUIDs
…eak vitest.config
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Dependency ReviewThe following issues were found:
|
| name: Production Deployment Gate | ||
| runs-on: ubuntu-latest | ||
| needs: build-and-test | ||
| if: github.ref == 'refs/heads/main' | ||
| if: github.ref == 'refs/heads/main' && github.event_name == 'push' | ||
|
|
||
| steps: | ||
| - name: All tests passed | ||
| run: echo "✅ All tests passed. Deployment can proceed." | ||
| deploy-to-vercel: | ||
| name: Deploy to Vercel | ||
| run: echo "✅ All tests passed. Production deployment can proceed." | ||
|
|
||
| # Deploy to production when PR is merged to main | ||
| deploy-production: |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
| name: Deploy to Production (Vercel) | ||
| runs-on: ubuntu-latest | ||
| needs: deployment-ready | ||
| if: github.ref == 'refs/heads/main' && success() | ||
| if: github.ref == 'refs/heads/main' && github.event_name == 'push' && success() | ||
|
|
||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v4 | ||
|
|
||
| - name: Deploy to Vercel | ||
| - name: Deploy to Vercel (Production) | ||
| uses: amondnet/vercel-action@v25 | ||
| id: vercel-production | ||
| with: | ||
| vercel-token: ${{ secrets.VERCEL_TOKEN }} | ||
| vercel-args: '--prod' | ||
| vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }} | ||
| vercel-org-id: ${{ secrets.VERCEL_ORG_ID }} | ||
| env: | ||
| VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }} | ||
|
|
||
| - name: Log production deployment | ||
| run: | | ||
| echo "🚀 Production deployment completed" | ||
| echo "Production URL: ${{ steps.vercel-production.outputs.preview-url }}" |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
…ge object directly
…sted and consistent
…inject a variable on global window for use in determining whether client script is running in e2e environment
…n context of modules called from astro.config.ts
…anging to use Playwright watcher
…m Consent/Preferences component, update tests
…nder() functions during build
…d when using vercel adapter
…le with Vercel adapter
…ated to pause() and resume()
…red-data e2e tests
| return html | ||
| .replace(/<script\b[^<]*(?:(?!<\/script>)<[^<]*)*<\/script>/gi, '') | ||
| .replace(/<iframe\b[^<]*(?:(?!<\/iframe>)<[^<]*)*<\/iframe>/gi, '') |
Check failure
Code scanning / CodeQL
Incomplete multi-character sanitization High
| return html | ||
| .replace(/<script\b[^<]*(?:(?!<\/script>)<[^<]*)*<\/script>/gi, '') |
Check failure
Code scanning / CodeQL
Incomplete multi-character sanitization High
| // Basic sanitization - remove script tags | ||
| // For production, install and use sanitize-html or DOMPurify | ||
| return html | ||
| .replace(/<script\b[^<]*(?:(?!<\/script>)<[^<]*)*<\/script>/gi, '') |
Check failure
Code scanning / CodeQL
Bad HTML filtering regexp High
…v server generally
…evelopment associated with e2e mock third-party service container work
…rty services, update package.json scripts and GitHub Actions CI workflows
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 23006535 | Triggered | Generic CLI Secret | 260e744 | test/containers/upstash/local-proxy/main.go | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
Description
Grab bag of work
Type of Change