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

Added

  • New FOSS Spotlight entry: Copy SMS Code – OTP Helper
  • Added otp-helper.png and otp-helper.webp to src/img/posts
  • Imported image assets via images.js as otphelpPng and otphelpWbp

Changed

  • Bumped version to v1.15.3

  • Updated Node.js version to v24.4.1 in .node-version and .nvmrc

  • Updated generator metadata in app.html to reflect SvelteKit 2.25.1

  • Updated "Last Updated" timestamp on FOSS Spotlight to 2025-07-20

  • Updated sitemap.xml with current post dates

  • Upgraded dependencies:

    • @sveltejs/adapter-netlify from ^5.0.2 to ^5.1.0
    • @sveltejs/kit from 2.22.5 to 2.25.1
    • @sveltejs/vite-plugin-svelte from ^6.0.0 to ^6.1.0
    • eslint-config-prettier from ^10.1.5 to ^10.1.8
    • eslint-plugin-jsdoc from ^51.3.4 to ^51.4.1
    • eslint-plugin-svelte from ^3.10.1 to ^3.11.0
    • stylelint from ^16.21.1 to ^16.22.0
    • svelte from 5.35.6 to 5.36.12
    • svelte-check from ^4.2.2 to ^4.3.0
    • svelte-eslint-parser from ^1.2.0 to ^1.3.0
    • vite from ^7.0.4 to ^7.0.5

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!

@netlify
Copy link

netlify bot commented Jul 21, 2025

Deploy Preview for networkpro-web ready!

Name Link
🔨 Latest commit 84caf3f
🔍 Latest deploy log https://app.netlify.com/projects/networkpro-web/deploys/687db84ccb02650008b9c8fe
😎 Deploy Preview https://deploy-preview-121--networkpro-web.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

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 test completion.

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.95)
  • Largest Contentful Paint (score: 0.36)
  • Speed Index (score: 0.94)
  • Time to Interactive (score: 0.81)
  • Largest Contentful Paint element (score: 0)
  • Links rely on color to be distinguishable. (score: 0)
  • Touch targets do not have sufficient size or spacing. (score: 0)
  • Serve static assets with an efficient cache policy (score: 0.5)
  • Reduce unused CSS (score: 0)
  • Reduce unused JavaScript (score: 0)
  • Avoid serving legacy JavaScript to modern browsers (score: 0.5)
  • Use efficient cache lifetimes (score: 0)
  • Optimize DOM size (score: 0)
  • Legacy JavaScript (score: 0.5)
  • 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 SunDevil311 merged commit bc2afd3 into master Jul 21, 2025
11 checks passed
@SunDevil311 SunDevil311 deleted the feature/foss-otp-helper branch July 21, 2025 03:51
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