Skip to content

Conversation

@SunDevil311
Copy link
Member

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

Changed

  • Updated GitHub workflows to specify ENV: ci where appropriate:
    • templates/check-codeql.template.yml
    • templates/publish.template.yml
    • auto-assign.yml
    • branch-backup.yml
    • check-security-txt-expiry.yml
    • dependency-review.yml
    • meta-check.yml
    • prevent-audit-merges.yml
    • secret-scan.yml
  • Added @sveltejs/adapter-netlify devDependency for smoother toggling between production and audit modes.
    • Production uses @sveltejs/adapter-vercel only. @sveltejs/adapter-netlify exists solely to support the audit environment.
  • Bumped project version to v1.25.10.
  • Updated dependencies:
    • @testing-library/svelte ^5.2.8^5.2.9
    • eslint-plugin-jsdoc ^61.1.12^61.2.0
    • posthog-js ^1.290.0^1.292.0

Removed

  • Removed unneeded comments in build-and-publish.yml workflow.

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
Copy link

vercel bot commented Nov 13, 2025

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

Project Deployment Preview Updated (UTC)
web Ready Ready Preview Nov 13, 2025 0:22am

Copy link
Member Author

@SunDevil311 SunDevil311 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All changes look good. Merging pending successful completion of tests.

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.96)
  • Largest Contentful Paint (score: 0.99)
  • Speed Index (score: 0.89)
  • Cumulative Layout Shift (score: 0.99)
  • Reduce initial server response time (score: 0)
  • Links rely on color to be distinguishable. (score: 0)
  • Reduce unused CSS (score: 0.5)
  • Document request latency (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.

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.87)
  • Largest Contentful Paint (score: 0.58)
  • Time to Interactive (score: 0.9)
  • 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 SunDevil311 merged commit cd73e42 into master Nov 13, 2025
11 of 13 checks passed
@SunDevil311 SunDevil311 deleted the feature/workflows branch November 13, 2025 01:15
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.

2 participants