chore: Update to the softlaunch patch release 4

[ari-nz]

No description provided.

[github-actions]

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

---

PR Review Complete ✅

I've reviewed PR #249: "chore: Update to the softlaunch patch release 4"

---

Summary

This is a clean, straightforward version bump PR that updates the HE-TME application version for the staging environment from 1.0.0-sl+3 to 1.0.0-sl+4 (softlaunch patch release 4).

✅ All checks passed:

• Linting (ruff format, ruff check, pyright, mypy): PASSED
• Commit message format: VALID (follows conventional commits)
• Test markers: N/A (constants file, no test functions)
• Code quality: EXCELLENT
• Architecture compliance: COMPLIANT

---

Change Details

File: tests/constants_test.py
Line: 75
Change:

- HETA_APPLICATION_VERSION = "1.0.0-sl+3"
+ HETA_APPLICATION_VERSION = "1.0.0-sl+4"

Scope: This constant is used across multiple E2E test modules:

• 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

Impact: Tests will now validate against the new softlaunch patch release 4 of the HE-TME application in the staging environment.

---

Review Findings

✅ Blocking Checks (All Passed)

1. Test Markers: N/A - This is a constants-only file with no test functions
2. Test Coverage: No change to coverage (constants file)
3. Code Quality: All linters passed

   ✓ ruff check: All checks passed
   ✓ ruff format: 152 files already formatted
   ✓ pyright: 0 errors, 0 warnings
   ✓ mypy: Success - no issues found in 80 source files
   

4. Conventional Commits: ✅ chore: prefix is correct for version bumps

✅ Architecture Compliance

• Modulith Principles: Not applicable (test constants)
• Dependencies: No changes to module dependencies
• Breaking Changes: None - backward compatible change

✅ Medical Device & Security

• No secrets or sensitive data exposed
• No changes to medical data handling
• Test environment only (staging)

✅ Documentation

• No documentation updates needed (internal test constant)
• Change is self-documenting in the PR title

---

Recommendations

Optional Enhancements (Non-blocking)

1. PR Description: Consider adding a brief description explaining:

   • What changed in softlaunch patch release 4
   • Why this version bump is needed
   • Any test behavior changes expected

   Example:

   Updates HE-TME staging version to 1.0.0-sl+4 to test against the latest softlaunch patch release.
   
   Changes in sl+4:
   - [Brief description of changes]
   
   Test Impact:
   - E2E tests will now validate against sl+4 in staging

2. CI Label: Per CLAUDE.md guidelines, consider adding the skip:test_long_running label to speed up CI execution if long-running tests aren't critical for this version bump.

---

Verification

I verified the following:

# ✅ Linting passes
make lint
# Result: All checks passed in ~60 seconds

# ✅ Constants file structure valid
pytest tests/constants_test.py --collect-only
# Result: 0 test items collected (expected - constants only)

# ✅ No unmarked tests (critical check)
# N/A - no test functions in this file

# ✅ Commit message format
git log --format="%s" -1
# Result: "chore: Update to the softlaunch patch release"
# Matches conventional commit format: type(scope): description

---

Conclusion

Recommendation: ✅ APPROVE

This PR is ready to merge. It's a clean, focused change that follows all repository standards and guidelines. The version bump will allow E2E tests to validate against the latest softlaunch patch release in staging.

No blocking issues found.
No required changes.

---

Next Steps

1. ✅ Merge when CI completes
2. 🔄 Monitor E2E test results in staging to ensure compatibility with sl+4
3. 📋 Consider adding the skip:test_long_running label if not already added

---

Great work on maintaining clean, focused commits! 🎉

---

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[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