chore: release prep for v1.25.8

[SunDevil311]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Added

• 🔐 Branch protection rules on master:
  • Enforced pull requests for all changes
  • Blocked force pushes
  • Linear history requirement
• 🚫 CI workflow to prevent merges from audit-netlify to master:
  • PRs originating from audit-netlify targeting master are automatically rejected
  • Triggered on pull_request events
  • Uses github.event.pull_request.head.ref for precise branch detection
• 🚀 Netlify CI deployment for audit-only branch:
  • Workflow .github/workflows/deploy-audit-netlify.yml added
  • Deploys audit-netlify to a separate Netlify site
  • Uses environmental variables to trigger vite build --mode audit
• 🌐 hooks.server.js CSP hardening for audit deployments:
  • Probely scanner detection based on UA/IP added via isProbelyScanner()
  • Audit-specific CSP disables analytics and CSP reporting endpoints
  • Logs detailed CSP info when in isAudit or isDebug modes
• 🛡️ Middleware improvements:
  • User-agent/IP fingerprinting for Probely DAST
  • Added logging for audit-mode scanner matches
• 🧪 Support for per-environment .env files (e.g. .env.audit)
• 🔄 Git helper scripts:
  • Added bash script to sync audit-netlify with latest master
  • Supports merge conflict resolution via VS Code diff viewer

Changed

• Updated .stylelintignore to exclude .netlify directory
• Updated lint:md script to exclude the build/ and .netlify/ directories
• Refined svelte.config.js to support alternate build targets (Vercel → Netlify via adapter switch)
• Audit builds now use isolated .env config and a separate Netlify site token

Checklist

• I have read and followed the guidelines in the CONTRIBUTING document.
• I've checked for existing Pull Requests for the same update/change.
• My code follows the project’s coding style.
• My code has been linted locally before submission.
• All new and existing tests pass.

 

• I have updated the documentation accordingly.
• I have added tests to cover my changes, if applicable. (Optional, especially for new contributors)

Pull requests are part of a collaborative process — we welcome contributions and review each one carefully. For all but the smallest changes, you can expect maintainers to request improvements or clarifications.

Please check back after opening your PR and be responsive to feedback so we can get your contribution merged quickly.

Thanks for helping improve Network Pro Strategies!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
web	Ready	Preview	Nov 11, 2025 9:55pm

[github-actions]

⚠️ Lighthouse Budget Issues Detected

• First Contentful Paint (score: 0.84)
• Largest Contentful Paint (score: 0.49)
• Speed Index (score: 0.99)
• Cumulative Layout Shift (score: 0.99)
• Time to Interactive (score: 0.87)
• Avoid multiple page redirects (score: 0)
• Largest Contentful Paint element (score: 0)
• Links rely on color to be distinguishable. (score: 0)
• Render blocking requests (score: 0)

View the full report in the workflow artifacts or in .lighthouseci/report.html.

[SunDevil311]

All changes look good. Merging.