chore: release prep for v1.25.7

[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

• Introduced src/lib/security/probely.js helper module to detect Probely vulnerability scanner requests via normalized IP and User-Agent matching.
  • Supports case-insensitive substring matching for known Probely UA fragments (ProbelySPDR/, etc.).
  • IP allowlisting based on published ranges: https://help.probely.com/en/articles/5112461/
• Added unit test suite tests/unit/server/lib/security/probely.test.js to verify robustness of isProbelyScanner() logic against UA/IP variations and edge cases.

Changed

• Updated hooks.server.js to integrate isProbelyScanner() as a drop-in replacement for inline Probely detection logic, improving clarity and testability.
• Contact details and motto updated in static/.well-known/humans.txt.
• Refreshed last modified dates in static/sitemap.xml.
• Minor cosmetic changes to static/robots.txt.
• Corrected fallback metadata in +layout.svelte.
• Removed inline styles from src/lib/components/PWAInstallButton.svelte and src/lib/components/foss/FossFeatures.svelte.
  • Moved styles to src/lib/styles/css/default.css.
  • Regenerated global.min.css bundle with LightningCSS.
• Minor optimizations and cleanup to several files:
  • src/lib/components/RedirectPage.svelte
  • src/lib/components/layout/Footer.svelte
  • src/lib/pages/AboutContent.svelte
  • src/lib/pages/TermsConditionsContent.svelte
  • src/lib/pages/TermsUseContent.svelte
  • src/routes/contact/+page.svelte
  • src/routes/posts/+page.svelte
  • src/routes/privacy-rights/+page.svelte
• Bumped project version to v1.25.7.
• Updated dependencies:
  • autoprefixer ^10.4.21 → ^10.4.22
  • browserslist ^4.27.0 → ^4.28.0
  • svelte 5.43.3 → 5.43.6
  • svelte-check ^4.3.3 → ^4.3.4
  • posthog-js ^1.285.1 → ^1.290.0
  • vite ^7.1.12 → ^7.2.2

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	Comments	Updated (UTC)
audit	Ready	Preview	Comment	Nov 11, 2025 0:18am
web	Ready	Preview	Comment	Nov 11, 2025 0:18am

[github-actions]

⚠️ Lighthouse Budget Issues Detected

• First Contentful Paint (score: 0.97)
• Largest Contentful Paint (score: 0.83)
• Time to Interactive (score: 0.97)
• Largest Contentful Paint element (score: 0)
• Links rely on color to be distinguishable. (score: 0)
• Reduce unused CSS (score: 0)
• Network dependency tree (score: 0)
• Render blocking requests (score: 0.5)

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

[SunDevil311]

All changes look good. Merging pending completion of tests.