To ensure a clean development approach, builds will be triggered by tag creation. Tags should be formatted as “v1.0.0-action/feature”. This SemVer-adjacent formatting follows a major, minor, patch standard followed by a systemic naming convention. This approach ensures clarity in tag tracking and historical milestones.
Added client-side watchdog to detect new builds by polling version.json and release-notes.json. On changes to version, build time, or release notes timestamp, the app now unregisters service workers, clears caches, and reloads to ensure users always see the latest release without manual cache clearing.
To ensure a clean development approach, builds will be triggered by tag creation. Tags should be formatted as “v1.0.0-action/feature”. This SemVer-adjacent formatting follows a major, minor, patch standard followed by a systemic naming convention. This approach ensures clarity in tag tracking and historical milestones.