v0.12.0 🚀

🚀 Enhancements

• Implement language translations for handling multi-language plugin (#915) @mimartinez
• Handle multiple index names in strapi config (#916) @L-Weisz

Thanks again to @L-Weisz and @mimartinez! 🎉

v0.11.1 🚀

• Add role permissions for the plugin (RBAC access control) (#892) @mimartinez
• Update dependabot config (#904) @brunoocasali

Thanks again to @brunoocasali, and @mimartinez! 🎉

v0.11.0 🚀

⚠️ Breaking changes

• Upgrade libraries & push node min version to 18 (#874) @brunoocasali & (#888) @curquiza

🚀 Enhancements

• Add task reporting after every async action in the strapi logs (#539) @bidoubiwa
• Sanitize private fields selectively (#850) @haZya
• Add id to getEntry return as fallback (#848) @matepaiva

Thanks again to @CaroFG, @bidoubiwa, @brunoocasali, @curquiza, @haZya, @matepaiva, @meili-bors[bot], and @nicolasvienot! 🎉

v0.10.0 🚀

⚠️ Changes

• Dropping node 14 support by removing node 14 CI tests in favor of node 18 (#807) @bidoubiwa
  It still works but not something we monitor.

🐛 Bug Fixes

• fix: getIndexes limited to 20 indexes (#818) @nicolasvienot

Thanks again to @CaroFG, @bidoubiwa, @brunoocasali, @nicolasvienot and @yannicschroeer! 🎉

v0.9.2 🚀

🔒 Security

⚠️ You may have private fields indexes in your Meilisearch instance, that is not the intended behavior.
⚠️ Update your strapi-plugin-meilisearch ASAP. When defining private fields, they should not be sent to Meilisearch since those indexed fields will be publicly available in public routes like /search.
⚠️ Reindex your collections.

• Fix data leaked of private fields: (#703) @brunoocasali

Other security fixes on yarn.lock:

• Bump json5 from 1.0.1 to 1.0.2 (#676)
• Bump minimist from 1.2.5 to 1.2.8 (#674)

Thanks again to @brunoocasali! 🎉

v0.9.1 🚀

⚠️ Breaking changes

• Create a custom _meilisearch_id field (#620) @bidoubiwa

🐛 Bug Fixes

• Fix multiple entity index update (#630) @aloulouamine

Thanks again to @Pablo-Aldana, @aloulouamine, @bidoubiwa ! 🎉

v0.8.2 🚀

🐛 Bug Fixes

• fix: issue causing TypeError: Cannot read properties of null (reading… (#597) @Kazdan1994

Thanks again to @Kazdan1994, @bidoubiwa and @meili-bors[bot]! 🎉

v0.8.1 🚀

This version makes this package compatible with Meilisearch v0.30.0 🎉
Check out the changelog of Meilisearch v0.30.0 for more information on the changes.

🐛 Bug Fixes

• Remove sensitive fields before transforming entries (#554) @MarekBodingerBA

Thanks again to @MarekBodinger, @MarekBodingerBA, @bidoubiwa, @brunoocasali, @lodisy, @meili-bors[bot] ! 🎉

v0.6.0-strapi-v3.0 🚀

Plugin version compatible with strapi-v3

The plugin version compatible with strapi v3 is now compatible with Meilisearch v0.29.1 🎉
Check out the changelog of Meilisearch v0.29.0 for more information on the changes.

to update:

npm update strapi-plugin-meilisearch@strapi_v3
# or 
yarn upgrade strapi-plugin-meilisearch@strapi_v3

Thanks again to @bidoubiwa! 🎉

v0.8.0 🚀

⚠️ Breaking changes

• Add entries query option in plugin configuration (#538) @bidoubiwa

Removal of populateEntryRule

The setting populateEntryRule in the plugin configuration is removed in favor of populate in entriesQuery (see next session).

Before:

{
  restaurant: { populateEntryRule: [] }
}

After:

{
  restaurant: { entriesQuery: { populate: [] }}
}

New plugin configuration: entriesQuery

It is possible with entriesQuery to define how your data will be fetched from your database. Here are the available options (plus locale from the internalization plugin).
See this readme section for further information.

Example

In plugin.js

module.exports = {
  meilisearch: {
    config: {
      restaurant: {
        entriesQuery: {
          limit: 1000, // batch size
          locale: 'all', // retrieve all languages
          ...
        }
      }
    }
  },
}

Thanks again to @bidoubiwa, and @meili-bors[bot]! 🎉