Automated release-health check. This issue is rewritten in place on every run and closed automatically once every gap below is closed; it is never duplicated.
Last evaluated: 2026-08-07T07:37:27.959204+00:00 (run)
unreleased-work — 3 releasable commit(s) unpublished for 4d 13h
main has been carrying 3 releasable commit(s) for 4d 13h past v0.15.0. main CI is green and no release run is in flight, so nothing is going to publish these on its own.
Next version would be a minor bump.
| commit |
bump |
age |
subject |
6f8a8dae |
patch |
4d 13h |
fix(ci): dispatch docs notification to renamed openadapt-ops repo (#100) |
38490d0c |
patch |
1d 8h |
fix: update vulnerable Python dependencies (#103) |
06e62661 |
minor |
1d 7h |
feat: guide qualification fault cases (#102) |
Most recent release run: 30637260941 — completed/success.
Publish with:
gh workflow run release.yml --repo OpenAdaptAI/openadapt-desktop --ref main -f operation=semantic-release
tag-without-release — 4 tag(s) published no release
4 tag(s) in the native lane exist with no GitHub release object. The tag is immutable and public; the artifacts it promises were never published.
cancelled and skipped are the outcomes no if: failure() step can see. A run cancelled while waiting on an environment approval gate lands here.
Re-run the publish with:
# Rebuild the installers for an existing engine version (X.Y.Z), then
# approve the native-release environment when the publish-draft job requests it.
gh workflow run native-freshness.yml --repo OpenAdaptAI/openadapt-desktop --ref main -f version=X.Y.Z
Everything the check considered and cleared
- [engine] openadapt-desktop 0.15.0 is on PyPI.
Reproduce locally with python scripts/check_release_health.py.
Automated release-health check. This issue is rewritten in place on every run and closed automatically once every gap below is closed; it is never duplicated.
Last evaluated:
2026-08-07T07:37:27.959204+00:00(run)unreleased-work— 3 releasable commit(s) unpublished for 4d 13hmainhas been carrying 3 releasable commit(s) for 4d 13h pastv0.15.0. main CI is green and no release run is in flight, so nothing is going to publish these on its own.Next version would be a minor bump.
6f8a8dae38490d0c06e62661Most recent release run:
30637260941— completed/success.Publish with:
tag-without-release— 4 tag(s) published no release4 tag(s) in the
nativelane exist with no GitHub release object. The tag is immutable and public; the artifacts it promises were never published.desktop-v0.1.029514474536failuredesktop-v0.7.029756479649cancelleddesktop-v0.8.029799291231cancelleddesktop-v0.12.030169968004failurecancelledandskippedare the outcomes noif: failure()step can see. A run cancelled while waiting on an environment approval gate lands here.Re-run the publish with:
Everything the check considered and cleared
Reproduce locally with
python scripts/check_release_health.py.