Update version for the next release (v0.19.0)

[meili-bot]

This PR is auto-generated.

The automated script updates the version of meilisearch-dart to a new version: "v0.19.0"

Summary by CodeRabbit

• Chores

  • Package version bumped to 0.19.0 and library-reported version updated.

• Documentation

  • Added a 0.19.0 changelog entry noting replication and sharding support.
  • Updated installation instructions to reference the 0.19.0 package version.

[coderabbitai]

📝 Walkthrough

Walkthrough

Bumped package version from 0.18.0 to 0.19.0 across metadata and source, updated README installation snippet, and added a new 0.19.0 section to CHANGELOG.md (including a "Breaking Changes" subsection marked None).

Changes

Cohort / File(s)	Summary
Package Version Updates pubspec.yaml, lib/src/version.dart	Package version and Version.current updated from 0.18.0 to 0.19.0.
Documentation CHANGELOG.md, README.md	Added # 0.19.0 changelog entry (includes "Changes" and "Breaking Changes: None"); README pubspec.yaml example updated to meilisearch: ^0.19.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A tiny hop, a version climb,
From 0.18 to 0.19 in time,
Changelogs penned and demos tweaked,
Docs aligned, the numbers peeked,
I nibble carrots, code looks prime.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: updating the package version from 0.18.0 to 0.19.0 for release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch meili-bot/bump-version

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 3-5: The changelog header jumps from a top-level H1 to H3 and
leaves the section empty; change the "### Breaking Changes:" heading to "##
Breaking Changes" and add explicit release note text such as "No breaking
changes." so the section isn't empty and follows proper heading hierarchy
(update the heading text "### Breaking Changes:" and insert "No breaking
changes." underneath).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2472038b-a254-45e2-938d-3dacc64ea2bd

📥 Commits

Reviewing files that changed from the base of the PR and between 4dfd59f and 3c262ee.

📒 Files selected for processing (4)

• CHANGELOG.md
• README.md
• lib/src/version.dart
• pubspec.yaml

[coderabbitai]

♻️ Duplicate comments (1)

CHANGELOG.md (1)

4-8: ⚠️ Potential issue | 🟡 Minor

Use ## subsection headings under the version header.

# 0.19.0 should be followed by ## headings (not ###) to avoid heading-level jumps (MD001). Also keep explicit release-note wording for breaking changes (e.g., “No breaking changes.”).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 4 - 8, The changelog uses level-3 headings after
the version header causing a heading-level jump; change the "### Changes:" and
"### Breaking Changes:" headings to "## Changes" and "## Breaking Changes"
respectively under the "# 0.19.0" header, and update the breaking-changes text
to an explicit release-note phrase like "No breaking changes." to match the
expected format.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@CHANGELOG.md`:
- Around line 4-8: The changelog uses level-3 headings after the version header
causing a heading-level jump; change the "### Changes:" and "### Breaking
Changes:" headings to "## Changes" and "## Breaking Changes" respectively under
the "# 0.19.0" header, and update the breaking-changes text to an explicit
release-note phrase like "No breaking changes." to match the expected format.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c99167fa-3d18-4b7f-9a5a-c3dffcf951bf

📥 Commits

Reviewing files that changed from the base of the PR and between 3c262ee and 881430f.

📒 Files selected for processing (1)

• CHANGELOG.md