Breaking API change - This release contains a minor API breaking change. Please read the following release notes before upgrading.
API breaking change
The JSON response format for creating API tokens via the API has changed to make the response consistent with other API routes.
If your integration only uses the token field from the response, no change is required. If your integration uses any other field from the response, those fields have moved from data.<key> to <key>.
For example, the response is now returned as a flat JSON object:
{"token": "...", "id": 123, ...}
instead of:
{"token": "...", "data": {"id": 123, ...}}
Improvements
- Improved the performance of several database queries, resulting in faster load times for multiple pages.
- Increased the maximum checklist depth to 9 levels, making checklists better compatible for CIS benchmarks and similar lists.
- Updated the container startup script to better support hardened container environments, including Kubernetes clusters with strict security policies.
- Added
Total research hoursas a placeholder.
Bug Fixes
- Fixed a 500 error that occurred when saving a webhook with a URL longer than 191 characters.
- Fixed an issue where full-day deadlines exported to calendar applications could appear as one day too long, especially in Outlook.
- Fixed a 500 error that occurred when using a scoped API token.
- Fixed the API token creation response format so it is consistent with other API routes.
- Fixed a compatibility issue that could cause queue workers to crash after a framework update.
- Fixed an issue where importing a checklist could incorrectly report that the checklist contained a duplicate code.
- Fixed an issue that prevented unused snippets from being deleted.
- Fixed placeholder options in components.