Release Pipeline Modernization

[MikeGarde]

Overview

This pull request significantly refactors the entire asset build, testing, and publication workflow. The primary goal is to modernize the CI/CD architecture, improve cross-platform compatibility, enhance robustness, and upgrade tooling dependencies to support Node.js v24 across all steps (CI and documentation).

Changes

• Refactored the release pipeline logic to centralize asset building and publishing, removing outdated manual scripts and deprecated workflows for better maintainability. (Commit 92d8739)
• Implemented sophisticated cross-platform target selection and testing within the build system. (Commit 92d8739)
• Updated CI configurations to explicitly use Node 24 for npm and GitHub Packages publishing, ensuring compatibility and avoiding runtime errors associated with older versions. (Commit 958d6e7)
• Standardized and modernized documentation headings and grammar throughout the setup guide for clearer cross-platform instructions. (Commit 958d6e7)

Testing / Validation

• Verification of successful asset build and publication across all supported target platforms is required post-merge.
• Confirm that local development environments utilizing Node 24 successfully trigger and complete the full release workflow pipeline.

Notes / Risks

• This represents a significant architectural change to how releases are structured. Thorough testing is recommended before merging into main.
• Users relying on deprecated build steps should validate their processes against the new centralized release mechanisms.

Commits in this PR:

• 958d6e7 Align CI and docs with Node 24 and Note tweaks
• 92d8739 Refactor release pipeline architecture

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.