Skip to content

v3.1.4

Choose a tag to compare

@likehopper likehopper released this 24 Oct 09:06
· 284 commits to 5305a7487773629b9908f8f8d8fe7451dbb59a8f since this release

Fix stale SLA caches when a calendar, schedule or holiday changes which competing level should apply.

  • Invalidate affected competing levels, including level creation and reassignment.
  • Preserve caches for calendar name/description and holiday name edits.
  • Capture dependencies before destruction, then remove dependent schedules and holiday links in bulk with Rails. Direct and nested child destruction keep their invalidation callbacks.
  • Preserve caches and configuration on rollback or aborted destruction, including reuse of the same instance.

On the regression fixtures, invalidation queries drop from 130 to 2 for calendar destruction and 17 to 3 for a holiday shared by seven calendars. Metadata edits issue zero invalidation queries. These measurements cover SQL workload, not production latency.

Validation: Redmine 5.1.13, 6.1.4 and 7.0.1, each with PostgreSQL 17.7, MariaDB 10.11.19 and strict MySQL 8.0.46. All five plugin suites passed; unit and controller suites were rerun after the final simplification: 9,936 tests, 55,119 assertions, zero failures/errors. The 12 skips are the expected migration tests on MySQL/MariaDB. The 35 invalidation tests check scope, rollback, nested edits, aborted destruction and SQL query counts. MySQL retains ONLY_FULL_GROUP_BY and both strict modes.

Details: test matrix, cache rules and workload measurements.

Upgrade: back up the database, update the plugin files and restart Redmine. Version 3.1.4 adds no migration relative to 3.1.3. When upgrading from 3.1.2 or older, also apply the existing reopened-issue fix with bundle exec rake redmine:plugins:migrate NAME=redmine_sla RAILS_ENV=production before restarting (migration 202111112021024). See the changelog.

No production deployment was performed.