chore: Bump the staging version of he-tme

[ari-nz]

No description provided.

[github-actions]

Claude finished @ari-nz's task —— View job

---

PR Review Complete ✅

Todo List:

• Read repository CLAUDE.md for standards
• Review the changed file (tests/constants_test.py)
• Check commit message format
• Verify test markers are present
• Run linting checks
• Validate version bump appropriateness
• Check for missing documentation/changes
• Provide comprehensive review feedback

---

Summary

This PR bumps the staging version of the he-tme application from 1.0.0-beta.8 to 1.0.0-sl+3. The change is isolated to a single test constant file and passes all linting checks.

✅ What Passed

1. Commit Message Format ✅

   • Follows conventional commits: chore: Bump the staging version of he-tme
   • Proper type (chore) and concise description

2. Linting ✅

   • All checks passed (ruff format, ruff check, pyright, mypy)
   • No code quality issues detected

3. Code Change ✅

   • Single line change in tests/constants_test.py:75
   • Only affects staging environment (case "staging":)
   • Production version remains unchanged at 1.0.0-beta.8

4. Test Markers ✅

   • All tests using HETA_APPLICATION_VERSION have proper markers (unit, integration, or e2e)
   • Verified files: application/gui_test.py, application/service_test.py, application/cli_test.py, platform/e2e_test.py, qupath/gui_test.py

⚠️ Minor Issue (Not Blocking)

Unmarked Test Found (unrelated to this PR):

• Location: tests/aignostics/platform/settings_test.py:198
• Test: test_custom_env_file_location
• Issue: Missing required test marker (@pytest.mark.unit, @pytest.mark.integration, or @pytest.mark.e2e)
• Impact: This test will NOT run in CI/CD because the pipeline explicitly filters by markers
• Fix: Add @pytest.mark.unit decorator before line 198:

@pytest.mark.unit
def test_custom_env_file_location(reset_cached_settings, record_property) -> None:
    """Test custom env file location."""

Note: This issue exists in origin/main and is not introduced by this PR. However, it should be addressed in a separate PR to ensure all tests run in CI.

📝 Suggestions (Non-Blocking)

1. Missing PR Description

   • Consider adding a description explaining:
     • Why the version bump is needed
     • What changed in he-tme v1.0.0-sl+3
     • Any testing performed with this version
   • This helps with traceability and future debugging

2. Version Format Observation

   • Staging: 1.0.0-sl+3 (uses sl pre-release + build metadata)
   • Production: 1.0.0-beta.8 (uses beta pre-release)
   • The sl appears to be a staging-specific pre-release identifier. Consider documenting this versioning convention in CLAUDE.md if not already documented.

🔍 Context for Reviewers

Files Using This Constant:
The HETA_APPLICATION_VERSION constant is used in 6 test files across the repository:

• tests/aignostics/application/gui_test.py
• tests/aignostics/application/service_test.py
• tests/aignostics/application/cli_test.py
• tests/aignostics/platform/e2e_test.py
• tests/aignostics/qupath/gui_test.py
• tests/constants_test.py

All these tests will now use the new version when running against the staging environment (AIGNOSTICS_PLATFORM_ENVIRONMENT=staging).

No Breaking Changes: This change only affects test execution in staging and does not impact production tests or the SDK's public API.

🚀 Recommendation

APPROVE - This PR is safe to merge. The change is:

• Minimal and isolated
• Properly formatted (linting passed)
• Only affects staging test environment
• Does not introduce any new issues

The unmarked test issue mentioned above is pre-existing and should be tracked separately.

---

Branch: chore/he-tme-version-bump

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud