Nouveautés | solidtime

21 oct. 2026Dernière nouveauté

v0.22.1

[!CAUTION] This is an urgent security release. Update as soon as possible!

This release updates the PHP version to 8.3.36 to fix two critical vulnerabilities CVE-2026-109618 (GHSA-w8hw-w9fx-j79w) and CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp)

With this release, FrankenPHP is also updated to version 1.13

Please update solidtime and any other PHP applications you are running immediately. You can find more details about the vulnerabilities here: https://www.php.net/index.php#2026-10-21-5

Source GitHub

19 oct. 2026

Goals

You can now add and track Goals for yourself inside of solidtime!

Goals let you set yourself a time target and follow your progress towards it, for example:

track at least 6 hours per day
spend 20 hours per week on a project
or keep meetings under 5 hours per week.

They have a target amount of hours within a specified period (day, week, month) and can be configured to be achieved if you surpass the target (e.g., a minimum of 20 hours worked per week on project X) or stay below the threshold (e.g., a maximum 10 hours with the tag meeting).

Goals support a wide range of filters including: projects, tasks, clients, tags, billability and type (work/break). To learn more about them check out our Goals Documentation.

We plan to bring more features & improvements to Goals soon!

Consistency changes/improvements

We made some changes to how reports are stored that only affect API users, this path was never achievable via the UI. If saved reports were stored with a member_ids filter of [] it never showed any data and was effectively broken. If any such reports exist they will now show like no member filter is applied. Additionally, saving new reports with a member filter of [] will be prohibited to make sure that there is only one state for "no filter applied". You can find the changes in https://github.com/solidtime-io/solidtime/pull/1287

Sending only a project_id update to a time entry via the API without setting the task_id back to null, could cause the project_id and task_id to be mismatched, this is fixed in https://github.com/solidtime-io/solidtime/pull/1290

DB_SSLMODE env variables were not picked up correctly by the deployments in recent versions. We therefore changed the env variable name to DB_SSL_MODE to potentially break existing instance configurations. If you want to force SSL_MODE for your database make sure to set DB_SSL_MODE. We updated our docs and examples to reflect that change.