Skip to content

Rc/v5.13.1 - #739

Merged
evilguy4000 merged 7 commits into
mainfrom
rc/v5.13.1
Aug 26, 2026
Merged

evilguy4000 merged 7 commits into
mainfrom
rc/v5.13.1

Conversation

@evilguy4000

Copy link
Copy Markdown
Collaborator

Description

Brief description of the change and why it's needed.

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would change existing behavior)
  • Documentation update
  • Refactor (no functional change)

Checklist

  • My code follows the project's style guidelines (Black, flake8).
  • I have added/updated tests for my changes.
  • All tests pass locally (e.g. pytest).
  • I have updated the documentation if needed.
  • For user-facing changes, I have added an entry to the Unreleased section of CHANGELOG.md.

Related issues

Fixes # (issue number, if applicable)


See CONTRIBUTING.md and CHANGELOG.md for guidelines.

Clients need a ready-to-install package with each version; the release workflow now zips the extension and uploads it alongside desktop and mobile artifacts.
…e a client to create one, and translate Create labels.
…ts (#722).

Credit last_active + idle_timeout on auto-stop, surface native web/extension notifications, and poll idle_notified from mobile while backgrounded so forgotten timers stop with the configured duration.
Reset searchable pickers to the committed selection on blur so typed-but-unselected text cannot look like a form change, and hide Create project until a client is chosen.
Track last_used_at on projects when timers start or manual entries are saved so pickers and API lists surface recent work ahead of alphabetical order (#738).
Re-apply canCreateGuard on the project picker so Issue #728 still blocks create-without-client after the last_used_at sorting change.
Syncs setup.py, desktop/package.json, mobile/pubspec.yaml, and
browser-extension manifests to 5.13.1. Adds the corresponding
CHANGELOG entry and README highlights for the release.
@evilguy4000
evilguy4000 merged commit f22e760 into main Aug 26, 2026
7 of 9 checks passed
@github-actions

Copy link
Copy Markdown

Database Migration Validation

✅ Migration validation passed!

Completed checks:

  • ✅ Migration consistency validation (with schema drift warnings)
  • ✅ Rollback safety test
  • ✅ Data integrity verification

The database migrations are safe to apply. 🚀

📝 Note: Schema drift warnings indicate existing model/migration mismatches that existed before this PR. These should be addressed in a separate schema alignment PR.


This comment was automatically generated by the Migration Validation workflow.

@github-actions

Copy link
Copy Markdown

❌ CI Test Results

Overall Status: 2 test suite(s) failed

Test Results: 3/9 passed

Test Suites:

  • ✅ Smoke Tests: success
  • ✅ Unit Tests: success
  • ⏸️ Integration Tests: cancelled
  • ✅ Security Tests: success
  • ❌ Code Quality: failure
  • ❌ Frontend Assets: failure
  • ⏭️ E2E, CSP & Accessibility: skipped
  • ⏭️ Docker Build: skipped
  • ⏭️ Full Test Suite: skipped

Commit: a530318
Workflow: 32953157120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant