Strapi v3.3.2 — Release Notes & Engineering Impact
Strapi v3.3.2. Source highlight: [core:database] fix: #8342 ignore dynamic zone component if its not in data (https://github.com/strapi/strapi/pull/8366) @iapain
348 tracked entries. Older history is imported progressively; see source coverage.
Strapi v3.3.2. Source highlight: [core:database] fix: #8342 ignore dynamic zone component if its not in data (https://github.com/strapi/strapi/pull/8366) @iapain
Strapi v3.3.1. Source highlight: [core:database] Fix polymorphic eager fetch (https://github.com/strapi/strapi/pull/8604) @alexandrebodin
Strapi v3.3.0. Source highlight: You can follow the migration guide here 🔥
Strapi v3.2.5. Source highlight: *These security issues are only exploitable by a user with admin panel access and the right permissions.*
Strapi v3.2.4. Source highlight: Migration Guide for this release: here
Strapi v3.2.3. Source highlight: [core:database] Fix undefined pk (https://github.com/strapi/strapi/pull/8260) @alexandrebodin
Strapi v3.2.2. Source highlight: [core:framework] Refactor log level configuration (https://github.com/strapi/strapi/pull/7695) @jiv-e
Strapi v3.2.1. Source highlight: [core:framework] Add support for brotli compression (https://github.com/strapi/strapi/pull/8169) @tanmoyopenroot
Strapi v3.2.0. Source highlight: **Draft and Publish** (@HichamELBSI @petersg83 @Convly @soupette @alexandrebodin)
Strapi v3.1.7. Source highlight: [admin] Update strapi-admin polish translation (https://github.com/strapi/strapi/pull/7507) @srflp
Strapi v3.1.6. Source highlight: [core:framework] Add privateAttributes to global and per model response (https://github.com/strapi/strapi/pull/7331) @dalbitresb12
Strapi v3.1.5. Source highlight: **Note**: Please note that the Users & Permissions on the left menu has been moved into the Settings menu per PR: #7467
Strapi v3.1.4. Source highlight: [admin] Add missing and improve existing German translations (https://github.com/strapi/strapi/pull/7383) @pr0gr8mm3r
Strapi v3.1.3. Source highlight: [documentation] Docs/parameters typos (https://github.com/strapi/strapi/pull/7238) @sebacampos
Strapi v3.1.2. Source highlight: [admin] Add the CheatSheet link (https://github.com/strapi/strapi/pull/7213) @Mcastres
Strapi v3.1.1. Source highlight: [core:framework] Updates webhooks RegExp to allow undescores, fixes #5543 (https://github.com/strapi/strapi/pull/7079) @msimmer
Strapi v3.1.0. Source highlight: Migration guide here
Strapi v3.0.6. Source highlight: [admin] Add Ukrainian translations for the whole project (https://github.com/strapi/strapi/pull/6223) @richardgrey
Strapi v3.0.5 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v3.0.4. Source highlight: [plugin:users-permissions] Fixes #6733 (https://github.com/strapi/strapi/pull/6738) @soupette
Strapi v3.0.3. Source highlight: [admin] Russian translation for Media Library (https://github.com/strapi/strapi/pull/6167) @alxnkt
Strapi v3.0.2. Source highlight: [admin] Add Malay(ms.json) Translation (https://github.com/strapi/strapi/pull/6394) @fadhilx
Strapi v3.0.1. Source highlight: [admin] Updates pt-BR locale (https://github.com/strapi/strapi/pull/6128) @adryan30
Strapi v3.0.0. Source highlight: **Migration Guide** here
Strapi v1.6.4. Source highlight: Ping the Studio URL instead of Google to allow China users to use the Studio without VPN.
Strapi v1.6.3 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.6.2. Source highlight: Use `new Promise()` pattern instead of `Promise.defer` in `strapi-generate-users`.
Strapi v1.6.1 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.6.0 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.7 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.4 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.3 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.2 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.1 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.5.0. Source highlight: Removed deprecated `dashboard` hook since the admin panel is now open-source.
Strapi v1.4.1. Source highlight: Wait GraphQL schemas generation before load `koa-graphql` middleware
Strapi v1.4.0. Source highlight: Load config from API and specific environment
Strapi v1.3.1. Source highlight: Disabled Studio connection in `production` environment
Strapi v1.3.0. Source highlight: Update to `[email protected]`
Strapi v1.2.0. Source highlight: Added `strapi link` command line to link an existing application without an `appId` to the Studio
Strapi v1.1.0. Source highlight: Be more permissive about Node.js and npm versions
Strapi v1.0.6. Source highlight: Bumped admin generator version
Strapi v1.0.5 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.0.4 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.0.3 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.0.2 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.0.1 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.
Strapi v1.0.0 is published, but the available notes are too limited to assess upgrade impact. Review the official source before upgrading.