Skip to content

chore: release prep for v1.27.2#224

Merged
SunDevil311 merged 1 commit intomasterfrom
chore/release-prep-v1.27.2
Apr 26, 2026
Merged

chore: release prep for v1.27.2#224
SunDevil311 merged 1 commit intomasterfrom
chore/release-prep-v1.27.2

Conversation

@SunDevil311
Copy link
Copy Markdown
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

  • Added a site-wide W3C Do Not Track tracking status resource at /.well-known/dnt.
  • Added the DNT tracking status resource to sitemap.xml.

Changed

  • Bumped project version to v1.27.2.
  • Updated npm run dev and npm run preview so they start local servers without automatically opening a browser.
  • Refreshed sitemap metadata for updated public pages and privacy well-known resources.
  • Updated the HeliBoard FOSS Spotlight GitHub link to the current HeliBorg/HeliBoard repository.
  • Excluded the human-readable DNT policy text file from Prettier formatting.

Removed

  • Removed stale commented debug logging from shared layout, metadata, legal, FOSS, PGP, services, terms, and home page components.
  • Removed /CNAME from the service worker ignored-path list.

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

vercel Bot commented Apr 26, 2026

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

Project Deployment Actions Updated (UTC)
web Ready Ready Preview Apr 26, 2026 3:14am

@github-actions
Copy link
Copy Markdown

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.8)
  • Largest Contentful Paint (score: 0.63)
  • Speed Index (score: 0.99)
  • Max Potential First Input Delay (score: 0.99)
  • Cumulative Layout Shift (score: 0.99)
  • Time to Interactive (score: 0.92)
  • Largest Contentful Paint element (score: 0)
  • Links rely on color to be distinguishable. (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)
  • Use efficient cache lifetimes (score: 0.5)
  • LCP request discovery (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.

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

@SunDevil311 SunDevil311 merged commit 6792870 into master Apr 26, 2026
12 checks passed
@SunDevil311 SunDevil311 deleted the chore/release-prep-v1.27.2 branch April 26, 2026 03:17
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.

1 participant