chore(leader): release 0.30.0

[arii]

Release PR

This PR contains the latest release.

0.30.0 (2026-02-08)

Features

• large: [REFACTOR] Centralize Redundant Heart Rate and Workout Type Definitions (#5677) (aeeacd8)
• large: Inconsistent HR Zone Calculation (Client vs. Dashboard) - Implement Zone-Aware Streaming (#6747) (d057be4)
• large: Refactor: Implement Unified Spotify Service Bus (#6044) (afc28cf)
• large: Refactor: Split vrt.spec.ts into Component-Specific Files (#5476) (c8e826c)
• medium: [REFACTOR] Standardize Duration Formatting Utilities (#5676) (f7de43a)
• medium: Enhance and Stabilize Unit Test Coverage for Core HRM Logic (#5458) (ce3bce4)
• medium: Fix Authentication Thrashing with Circuit Breaker (#6068) (2d06a36)
• medium: Fix Critical State Management and Data Recording Issues (#5417) (a1a84b1)
• medium: Fix Spotify Playlist Track Selection (#6076) (4a8db60)
• medium: Gender-Inclusive Calorie Estimation (#5433) (fb52bf0)
• medium: Refactor and Test useWorkoutSessionManager (#6094) (c041273)
• medium: Refactor and Validate Calorie Calculation Logic (#6104) (d1d431f)
• small: Enable Automatic Workout Data Persistence on /client/connect Page (#5659) (a7644c9)
• small: Fix Bluetooth Auto-Connect Infinite Loop (#6042) (de7e903)
• small: Fix Spotify Playlist Track Crash (#5413) (d716cbf)
• small: Move Refresh Button to Improve Vertical Spacing (#6238) (ec67c69)
• testing: add unit tests for core utility functions (#5435) (d68649f)

Bug Fixes

• bluetooth: Prevent race condition in GATT connection (#6075) (8442db7)
• critical: Ensure verdict field always present in Gemini review results (#5837) (c2d9302)

---

This PR was generated with Release Please. See documentation.

[arii]

Reviewed commit: f790cff0fc25e5ff26499d4a3939168aacbf6247

Summary

This Pull Request is a chore release, updating the project version from 0.29.0 to 0.30.0. The changes correctly reflect the new version in the .release-please-manifest.json file and append the new release entry to the docs/CHANGELOG.md.

Verification

I have verified the following:

• Version Update: The .release-please-manifest.json file has been updated to 0.30.0 as expected for a release PR.
• Changelog Entry: The docs/CHANGELOG.md file correctly includes a new entry for version 0.30.0, documenting the "Fix Spotify Playlist Track Crash" feature (#5413). The format and content adhere to standard changelog practices.
• No Functional Code Changes: This PR does not introduce any functional code changes, new features, or bug fixes beyond the metadata updates related to the release process itself. The "TEST COVERAGE ALERT" is noted but not applicable here as no source code logic was altered.

Conclusion

No issues or regressions were found. The changes are consistent with a routine release process and are correctly applied.

Reviewed at commit: f790cff0fc25e5ff26499d4a3939168aacbf6247

[arii]

Reviewed commit: bc0f05a15fa3b4db0036db9a80fffc20c7d51c63

This Pull Request chore(leader): release 0.30.0 correctly updates the project's release manifest (.release-please-manifest.json) and the CHANGELOG.md for version 0.30.0. These changes are consistent with a standard automated release process. The PR itself does not introduce any functional code changes, new features, or bug fixes; it merely records the outcome of previously merged work. The features listed in the changelog (issues #5417 and #5413) would have been reviewed and tested in their respective Pull Requests. The 'TEST COVERAGE ALERT' is not applicable to this administrative release PR, as no source code was modified directly to introduce new functionality. Verified that the version numbers are correctly incremented from 0.29.0 to 0.30.0 in both the manifest and the changelog. The changelog entries are appropriately formatted.

Reviewed at commit: bc0f05a15fa3b4db0036db9a80fffc20c7d51c63

[arii]

Reviewed commit: 037512c69b07e717bd2438b6f6c35f35f5efa0da

Summary

This PR is an automated release commit for version 0.30.0. It updates the .release-please-manifest.json file to reflect the new version and adds the corresponding entries to docs/CHANGELOG.md. The changelog correctly lists the features and bug fixes incorporated in this release, including critical state management fixes, a Spotify crash fix, and new unit tests.

Strengths

• Automated Release: The changes are consistent with an automated release process, ensuring consistency in versioning and changelog updates.
• Correct Versioning: The version is correctly bumped from 0.29.0 to 0.30.0 in the manifest.
• Comprehensive Changelog: The CHANGELOG.md is updated with appropriate entries for features, linking to the respective PRs/issues and commits, which is great for release transparency.

Issues

No issues found. The PR correctly performs its function as an automated release.

Test Coverage

This PR primarily updates metadata files (.release-please-manifest.json, docs/CHANGELOG.md) and does not introduce functional code changes. Therefore, no new tests are required as part of this PR. The changelog itself indicates that unit tests for core utility functions were added in a previous PR (#5435), which is good.

Recommendations

None. The PR is straightforward and correct.

Verdict

✅ Verified the version bump in .release-please-manifest.json and the updated CHANGELOG.md for 0.30.0. No regressions found. Ready for approval.

Reviewed at commit: 037512c69b07e717bd2438b6f6c35f35f5efa0da

[arii]

Reviewed commit: dccafdded3953e9f8a9b231cc6254359c8181670

This PR is a chore release, bumping the version from 0.29.0 to 0.30.0. The changes in release-please-manifest.json and docs/CHANGELOG.md are consistent with a standard release process. The CHANGELOG.md correctly reflects the new version and lists the features and fixes included in this release, such as critical state management fixes, automatic workout data persistence, Spotify playlist track fix, and new unit tests for core utilities.

The 'TEST COVERAGE ALERT' is noted, but given that this PR only modifies release manifest files and the changelog (documentation), it does not involve changes to application source code that would necessitate new tests. Therefore, the alert is not applicable in this context.

All changes are as expected for a release PR. No functional code changes were introduced that would require a deeper review of architecture, security, or performance.

Reviewed at commit: dccafdded3953e9f8a9b231cc6254359c8181670

[arii]

Reviewed commit: 787fd3a015ccf5c2705fd3180aaa4e32655897bf

This PR is a routine release chore, bumping the project version to 0.30.0.

Verification:

• Verified the .release-please-manifest.json file has been correctly updated from 0.29.0 to 0.30.0.
• Verified the docs/CHANGELOG.md file includes the new 0.30.0 entry with the associated features, fixes, and testing updates.

These changes are consistent with the automated release-please workflow and do not introduce any functional code changes or regressions. The 'TEST COVERAGE ALERT' is expected for a release PR as it primarily updates metadata and documentation.

Reviewed at commit: 787fd3a015ccf5c2705fd3180aaa4e32655897bf

[arii]

Reviewed commit: c9d807db33a9ecc04db9fe0c3dbd3710f2776f36

This pull request is a chore(leader): release 0.30.0, primarily updating the project's version and changelog.

Changes Verified

1. Version Bump: The .release-please-manifest.json file has been correctly updated from 0.29.0 to 0.30.0, reflecting the new release version.
2. Changelog Update: The docs/CHANGELOG.md file has been updated to include a comprehensive list of features and bug fixes for version 0.30.0. The entries are well-formatted and categorize the changes appropriately.
   • Features include: several refactors for centralizing definitions, splitting VRT tests, standardizing duration formatting, fixing state management issues, enabling workout data persistence, fixing a Spotify crash, and adding unit tests.
   • Bug Fixes include: a critical fix to ensure the verdict field is always present in Gemini review results.

Given that this is an administrative release PR and no functional code changes were introduced, the "TEST COVERAGE ALERT" is not applicable in this context. The updates to the changelog accurately reflect the work completed for this release.

Verdict

This PR is in good shape and ready for approval.

Reviewed at commit: c9d807db33a9ecc04db9fe0c3dbd3710f2776f36

[arii]

📋 Quality Gate Results

Check	Status
Knip	✅ success
Lint	✅ success
Build	✅ success
Infra Tests	✅ success
Unit Tests	✅ success
Component Tests	✅ success
Perf Tests	✅ success
Visual Tests	❌ failure

❌ Visual Test Failure Details

    test-results/vrt-connect-page-Visual-Re-7a8f6-Page-no-devices-found-state-chromium-retry2/test-failed-1.png
    ────────────────────────────────────────────────────────────────────────────────────────────────

    attachment #3: video (video/webm) ──────────────────────────────────────────────────────────────
    test-results/vrt-connect-page-Visual-Re-7a8f6-Page-no-devices-found-state-chromium-retry2/video-1.webm
    ────────────────────────────────────────────────────────────────────────────────────────────────

    attachment #4: video (video/webm) ──────────────────────────────────────────────────────────────
    test-results/vrt-connect-page-Visual-Re-7a8f6-Page-no-devices-found-state-chromium-retry2/video.webm
    ────────────────────────────────────────────────────────────────────────────────────────────────

    Error Context: test-results/vrt-connect-page-Visual-Re-7a8f6-Page-no-devices-found-state-chromium-retry2/error-context.md

  4) [chromium] › tests/playwright/remote-capabilities.spec.ts:8:3 › Remote Capabilities & Command Relay › Controller sends commands via WebSocket 

    Error: expect(received).toContainEqual(expected) // deep equality

    Expected value: ObjectContaining {"command": "PAUSE", "type": "SPOTIFY_COMMAND"}
    Received array: [{"type": "GET_STATE"}, {"restDuration": 10, "type": "TIMER_CONFIG", "workDuration": 20}, {"role": "controller", "type": "REGISTER_CLIENT"}, {"command": "GET_DEVICES", "type": "SPOTIFY_COMMAND"}, {"restDuration": 10, "type": "TIMER_CONFIG", "workDuration": 20}, {"command": "START", "type": "TIMER_COMMAND"}, {"command": "NEXT", "type": "SPOTIFY_COMMAND"}, {"restDuration": 10, "type": "TIMER_CONFIG", "workDuration": 20}, {"command": "START", "type": "TIMER_COMMAND"}, {"command": "NEXT", "type": "SPOTIFY_COMMAND"}]

    Call Log:
    - Timeout 5000ms exceeded while waiting on the predicate

      70 |     await stopButton.click()
      71 |     // 5. Verify WebSocket Command
    > 72 |     await expect
         |     ^
      73 |       .poll(() => sentMessages)
      74 |       .toContainEqual(
      75 |         expect.objectContaining({
        at /home/runner/work/hrm/hrm/tests/playwright/remote-capabilities.spec.ts:72:5

    attachment #1: screenshot (image/png) ──────────────────────────────────────────────────────────
    test-results/remote-capabilities-Remote-442e2-ends-commands-via-WebSocket-chromium/test-failed-1.png
    ────────────────────────────────────────────────────────────────────────────────────────────────

    attachment #2: video (video/webm) ──────────────────────────────────────────────────────────────
    test-results/remote-capabilities-Remote-442e2-ends-commands-via-WebSocket-chromium/video.webm
    ────────────────────────────────────────────────────────────────────────────────────────────────

    Error Context: test-results/remote-capabilities-Remote-442e2-ends-commands-via-WebSocket-chromium/error-context.md

  3 failed
    [chromium] › tests/playwright/vrt-connect-page.spec.ts:18:3 › Visual Regression Tests for /client/connect Page › scanning state 
    [chromium] › tests/playwright/vrt-connect-page.spec.ts:54:3 › Visual Regression Tests for /client/connect Page › connection error state 
    [chromium] › tests/playwright/vrt-connect-page.spec.ts:69:3 › Visual Regression Tests for /client/connect Page › no devices found state 
  1 flaky
    [chromium] › tests/playwright/remote-capabilities.spec.ts:8:3 › Remote Capabilities & Command Relay › Controller sends commands via WebSocket 
  15 passed (6.1m)
 ELIFECYCLE  Command failed with exit code 1.

⚠️ Some checks failed. Full logs available in workflow artifacts.

---

Report generated for commit: eb7f38ed667043556e34d980d6fec53a074b6105

[arii]

Reviewed commit: c12b5f6e4cee1635aead12636927e5960690bea1

This PR is a standard release commit generated by the release-please action, updating the project version to 0.30.0.

Strengths

• Adherence to Release Process: The PR correctly updates .release-please-manifest.json and docs/CHANGELOG.md, reflecting the new version and summarizing merged features and bug fixes. This aligns with the automated changelog process described in docs/DEVELOPMENT.md under "Commit Message Standards".
• Changelog Quality: The CHANGELOG.md entries are well-structured, referencing specific PRs and categorizing changes into 'Features' and 'Bug Fixes' with appropriate scopes (large, medium, small, testing, critical).
• No Functional Code Changes: As expected for a release chore, no functional code has been modified, minimizing the risk of introducing new bugs or regressions.

Issues

No issues found. The changes are purely for versioning and documentation, and they are correct.

Test Coverage

The "TEST COVERAGE ALERT" is a false positive for this type of PR. Release commits typically do not involve changes to source code that would require corresponding test updates. The changes are confined to metadata files (.release-please-manifest.json and docs/CHANGELOG.md).

Verdict

✅ Verified the version update and changelog content. No regressions or architectural concerns found. Ready for approval.

Reviewed at commit: c12b5f6e4cee1635aead12636927e5960690bea1

[arii]

Reviewed commit: 5750625f7e627ff6d0c96d25ccb0afa523e4665e

This Pull Request is a standard chore(leader): release PR, automatically generated by release-please to update the project version and changelog.

Review Summary

• The .release-please-manifest.json file has been correctly updated from 0.29.0 to 0.30.0.
• The docs/CHANGELOG.md file now includes the new 0.30.0 section, detailing features and a critical bug fix merged since the last release. This adheres to the Conventional Commits specification, as outlined in docs/DEVELOPMENT.md (Commit Message Standards).
• The "TEST COVERAGE ALERT" is expected for this type of PR, as it only modifies release metadata and documentation, not functional source code that would require new tests. Therefore, this alert is not a concern for this specific change.

All changes are consistent with a routine release process. No functional code changes were introduced that would require deeper architectural, security, or performance review based on project guidelines.

Reviewed at commit: 5750625f7e627ff6d0c96d25ccb0afa523e4665e

[arii]

Reviewed commit: 637b302e93a5cacc37187646fc700dc31f8c1630

This PR is a routine release update to version 0.30.0. It correctly updates the .release-please-manifest.json and docs/CHANGELOG.md to reflect the new version and its associated features and bug fixes. No functional code changes were introduced by this PR itself, making the review straightforward.

Strengths

• Automated Release Process: The changes to release-please-manifest.json and CHANGELOG.md indicate a well-established and automated release process, which helps maintain consistency and reduces manual errors.
• Clear Changelog: The CHANGELOG.md is well-formatted and includes specific commit hashes and PR links for each feature and bug fix, providing excellent traceability.

Issues

No issues found. This PR is a standard version bump and changelog update.

Test Coverage

The review context indicates a "TEST COVERAGE ALERT" for modified source code without corresponding test changes. However, for a chore(leader): release PR, the files modified (.release-please-manifest.json and docs/CHANGELOG.md) are release artifacts and documentation. These files do not contain functional application logic that would require unit or integration tests. Therefore, the absence of new or updated tests is expected and appropriate for this type of PR.

Verdict

Verified the version bump and changelog updates. No functional code changes or regressions were introduced. This PR is ready for approval.

Reviewed at commit: 637b302e93a5cacc37187646fc700dc31f8c1630

[arii]

Reviewed commit: a68c6114bfdf5bd658f2d6eb803496c15e4efc4c

This PR performs a standard release update to version 0.30.0.

Code Changes

• The .release-please-manifest.json file has been updated to reflect the new version 0.30.0.
• The docs/CHANGELOG.md has been correctly updated with all changes included in the 0.30.0 release, following the Conventional Commits specification.

Test Coverage

The "TEST COVERAGE ALERT" is noted. However, since this PR only modifies release manifest and changelog files, no corresponding test changes are required. The alert is a false positive in this specific context.

Conclusion

The changes are appropriate for a release PR. The version bumps are correct, and the changelog is properly populated. No functional code was changed, thus no new issues or regressions are introduced.

Reviewed at commit: a68c6114bfdf5bd658f2d6eb803496c15e4efc4c

[arii]

Reviewed commit: 6a2354bb772ac5134cabf79676bcdac180b8363a

This PR appears to be a standard chore for the 0.30.0 release. The .release-please-manifest.json correctly reflects the version bump, and the docs/CHANGELOG.md has been automatically updated with all the features and bug fixes merged since the last release. This aligns with the expected behavior of the release-please workflow.

However, I noticed the removal of the "test:slop" script from package.json. Given the project's strong emphasis on "AI Slop Prevention" as detailed in .github/copilot-instructions.md (which is a critical architectural constraint), the removal of a dedicated test for "slop" needs clarification. Please provide context on why this script was removed and if its functionality has been integrated elsewhere or deemed obsolete.

Reviewed at commit: 6a2354bb772ac5134cabf79676bcdac180b8363a

[arii]

Reviewed commit: ee30845218d9daa94e3b70e85933217bc3dced5e

This PR chore(leader): release 0.30.0 correctly updates the project version to 0.30.0.

Strengths

• The .release-please-manifest.json file has been updated to reflect the new version 0.30.0.
• The docs/CHANGELOG.md has been correctly updated with a new section for 0.30.0, listing all features and bug fixes included in this release. The formatting and links appear consistent with previous entries.

Issues

• None.

Test Coverage

The automated "TEST COVERAGE ALERT" is noted. However, this PR modifies only release metadata files (.release-please-manifest.json and docs/CHANGELOG.md), not functional source code. Therefore, no corresponding test changes are expected or required for this type of PR.

Verdict

The changes are purely for release management and are correctly applied. This PR is ready for approval.

Reviewed at commit: ee30845218d9daa94e3b70e85933217bc3dced5e

[arii]

Reviewed commit: b64f43da5caa6cdb77467b6ef534c9b9d0e7ddd0

This PR is an automated release chore for version 0.30.0.

Strengths

• Automated Release: The PR correctly updates the .release-please-manifest.json to 0.30.0 and populates the docs/CHANGELOG.md with all features and bug fixes included in this release. This aligns with the project's automated release process.
• No Functional Code Changes: As expected for a release PR, there are no functional code changes, only metadata updates.

Issues

• Test Coverage Alert Misleading: The "TEST COVERAGE ALERT" is not applicable to this PR, as it only involves version bumps and changelog updates, not functional code modifications. This is a minor observation and does not block the PR.

Verdict

This PR is a standard, automated release. The changes are as expected and correctly reflect the new version. It is ready for approval.

Reviewed at commit: b64f43da5caa6cdb77467b6ef534c9b9d0e7ddd0

[arii]

Reviewed commit: c0a71db4c7f4c6fd860fc6e4032ce53be0d03bd5

This Pull Request chore(leader): release 0.30.0 correctly updates the .release-please-manifest.json to version 0.30.0 and adds the corresponding changelog entries to docs/CHANGELOG.md.

Strengths

• Accurate Versioning: The release manifest and changelog reflect the intended version update.
• Comprehensive Changelog: The new 0.30.0 section in the changelog includes a detailed list of features and bug fixes with relevant issue links and commit hashes.

Issues

• No functional code changes were introduced in this PR, making the "TEST COVERAGE ALERT" a false positive in this context. The changes are purely administrative for the release process.

Test Coverage

• Not applicable, as this PR only updates release metadata and documentation, with no changes to source code or tests.

Verdict

• This PR is ready for approval.

Reviewed at commit: c0a71db4c7f4c6fd860fc6e4032ce53be0d03bd5