v11.9.2
π Bug Fixes & Optimizations
- @directus/app
- @directus/api
- Fixed
requireSelectioncheck for manual trigger flows (#25386 by @JoshTheDerf)
- Fixed
π¦ Published Versions
@directus/app@13.11.2@directus/api@28.0.2
requireSelection check for manual trigger flows (#25386 by @JoshTheDerf)@directus/app@13.11.2@directus/api@28.0.2
Added support for LDAP login and enhanced parameter consistency for refresh/logout commands. Allowed overriding the mode in refresh and logout commands to be inline with login (#25132)
The login method now accepts a payload object instead of separate email and password parameters.
This enables support for both standard and LDAP authentication, but requires updates to code that previously called sdk.login(email, password).
The new usage is sdk.login({ email, password }) or sdk.login({ identifier, password }) for LDAP.
The refresh and logout command method parameters have been updated to be consistent across usage. The functions now accept an options object instead of their previous regular parameters.
For example the new usage for refresh is sdk.request(refresh({ mode: "json", refresh_token })) instead of sdk.request(refresh('json', refresh_token)).
AUTH_.+_ISSUER_DISCOVERY_MUST_SUCCEED and AUTH_.+_CLIENT_HTTP env variables to the openid provider (#25002 by @ComfortablyCoding)backlink query parameter to exclude back-relations when expanding *.* in the fields query parameter (#25284 by @Nitwel)AUTH_.+_ISSUER_DISCOVERY_MUST_SUCCEED and AUTH_.+_CLIENT_HTTP env variables to the openid provider (#25002 by @ComfortablyCoding)items.sort action hook (#25340 by @ComfortablyCoding)info.version in the OpenAPI specs (#25353 by @br41nslug)numeric_precision, numeric_scale and max_length not respected on schema changes (#25346 by @ComfortablyCoding)@directus/app@13.11.0@directus/api@28.0.0@directus/components@1.1.1@directus/composables@11.2.0create-directus-extension@11.0.15@directus/env@5.1.0@directus/errors@2.0.2@directus/extensions@3.0.7@directus/extensions-registry@3.0.7@directus/extensions-sdk@14.0.0@directus/memory@3.0.6@directus/pressure@3.0.6@directus/schema-builder@0.0.3@directus/storage-driver-azure@12.0.6@directus/storage-driver-cloudinary@12.0.6@directus/storage-driver-gcs@12.0.6@directus/storage-driver-s3@12.0.6@directus/storage-driver-supabase@3.0.6@directus/system-data@3.1.1@directus/themes@1.1.2@directus/types@13.2.0@directus/utils@13.0.7@directus/validation@2.0.6@directus/sdk@20.0.0
Warning
Breaking change: Due to the security reason, the "Console" feature is now disabled by default. If you need this feature and understand the risk, you can enable it via the environment variable DOCKGE_ENABLE_CONSOLE=true.
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has
s been included in one of the pull requests.
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
Assume that you have 4 Dockge instances currently.
New Agent.Dockge 1. Dockge 2/3/4 are connected from Dockge 1.Dockge 1 works like a proxy, it will forward requests/responses from Dockge 2/3/4 to your browser.
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
Open dockge's compose.yaml and change the image tag from 1 to beta like:
... services: dockge: image: louislam/dockge:beta ...
And then update and restart the stack:
docker compose pull docker compose up -d
Assume that you have 4 Dockge instances currently.
Dockge 1. Dockge 2/3/4 are connected from Dockge 1.Dockge 1 works like a proxy, it will forward requests/responses from Dockge 2/3/4 to your browser.
Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
\r\n (Thanks @syko9000)${PORT}Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.
.env file (Thanks @syko9000)pnpm run reset-password, which is used for resetting your password.
This release contains the following fixes and changes:
Routine release.
Full Changelog: 2025-01-26...2025-06-03
This is a bug-fix release for FreshRSS 1.26.x
A few highlights β¨:
This release has been made by @Alkarex, @Inverle and newcomers @CarelessCaution, @the7thNightmare
Full changelog:
bgcolor, text, background, link, alink, vlink #7606
directus_files (#25241 by @Nitwel)dist folder to the build command (#25129 by @licitdev)ip, userAgent and origin for ws activity (#25114 by @ComfortablyCoding)ip, userAgent and origin for ws activity (#25114 by @ComfortablyCoding)ADMIN_PASSWORD, ADMIN_TOKEN, KEY, and SECRET to always be interpreted as strings (#25196 by @the-other-dev)@directus/app@13.10.0@directus/api@27.1.0@directus/composables@11.1.11create-directus-extension@11.0.14@directus/env@5.0.5@directus/extensions@3.0.6@directus/extensions-registry@3.0.6@directus/extensions-sdk@13.1.1@directus/memory@3.0.5@directus/pressure@3.0.5@directus/schema-builder@0.0.2@directus/storage-driver-azure@12.0.5@directus/storage-driver-cloudinary@12.0.5@directus/storage-driver-gcs@12.0.5@directus/storage-driver-s3@12.0.5@directus/storage-driver-supabase@3.0.5@directus/themes@1.1.1@directus/types@13.1.2@directus/utils@13.0.6@directus/validation@2.0.5
If you are using Part-DB it would be helpful if you fill out this short survey on your usage of Part-DB (Google Forms): https://forms.gle/Q15twx3YYq3qCNfe8
There is a new experimental docker image, which is much faster. See this post for more info.
You can help to translate Part-DB to other languages. See this post for more info.
Until this version, users could upload SVG files containing JS code, that would be executed if a user opened the SVG in a new tab, allowing for a XSS vulnerability. This was only possible if the SVG files were explicitly opened in a new tab, if the file was embedded inside a Part-DB tab, then there was no risk.
Since this version, SVG files gets sanitized during upload, to prevent any JS code execution. If you have existing SVG files, you can sanitize them, by running the console command php bin/console partdb:attachments:sanitize-svg.
If you are using Part-DB with nginx, you should add the following block to your server configuration, to further harden it by setting a content security policy for SVG files.
# Set Content-Security-Policy for svg files, to block embedded javascript in there
location ~* \.svg$ {
add_header Content-Security-Policy "default-src 'self'; script-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; frame-ancestors 'none';";
}
For apache, this is done automatically in the .htaccess file of Part-DB.
Full Changelog: v1.17.0...v1.17.1
This release contains the following fixes and changes: