Skip to content

Rc/v5.17.0 - #765

Merged
evilguy4000 merged 5 commits into
mainfrom
rc/v5.17.0
Sep 23, 2026
Merged

evilguy4000 merged 5 commits into
mainfrom
rc/v5.17.0

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.

…al (#760)

Users who forget to start a timer can backdate it when starting from the dashboard, matching the /timer page. Invalid overrides redirect back to the submitting page.
)

Let admins pick review (keep running) or auto_stop (credit idle window) so forgotten timers match the behavior users expect across web, extension, desktop, and mobile.
Make exported invoice PDFs pass EN 16931 and PDF/A-3b validators by embedding Liberation fonts, fixing CII XML structure/VAT categories, and adding structured addresses with pre-export checks.
Add GDPR erasure, weekly goals/recurring tasks/project-template APIs, estimates vs actuals, OAuth/SCIM scaffolding, and Mollie/XRechnung stubs; tighten security and UI consistency while removing dead refactored route modules.
Promote Unreleased notes into the 5.17.0 changelog entry, add README
highlights, align VERSION and desktop/extension/mobile clients, and
refresh GAP_ROADMAP version references.
@evilguy4000
evilguy4000 merged commit 3a3ea53 into main Sep 23, 2026
13 of 15 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: 1ba3e07
Workflow: 35843557149

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