chore(docker): bump DIKW_VERSION to v0.6.5

[helebest]

Auto-generated by release.yml after publishing v0.6.5 to PyPI.

The Dockerfile's DIKW_VERSION must match a version already on PyPI
because the Trivy PR-scan job builds the image and pip installs
from PyPI. This PR closes the drift window that opens between the
pyproject.toml version bump and the wheel landing on PyPI.

CI note: when the RELEASE_PR_PAT secret is configured this PR
is opened with it, so ci.yml/Trivy run automatically. If the secret
is unset the PR falls back to the default GITHUB_TOKEN, whose PRs
cannot trigger other workflows — then push an empty commit (or
close/re-open) to run the gate, or (with admin) merge directly
(single-line change; the post-publish guard in reusable-ci.yml
re-validates on the next PR).

Summary by CodeRabbit

• Chores
  • Updated the Docker example to use a newer package version, which will install the latest compatible dikw-core[postgres] release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9285d514-09de-4d97-8a32-5023d9f16c91

📥 Commits

Reviewing files that changed from the base of the PR and between f8c1045 and 76f3062.

📒 Files selected for processing (1)

• examples/docker/Dockerfile

---

📝 Walkthrough

Walkthrough

The DIKW_VERSION build argument in examples/docker/Dockerfile is bumped from 0.6.4 to 0.6.5, which changes the version of dikw-core[postgres] installed during the Docker image build.

Dockerfile version bump

Layer / File(s)	Summary
DIKW_VERSION bump examples/docker/Dockerfile	ARG DIKW_VERSION default changed from 0.6.4 to 0.6.5, updating the pip install dikw-core[postgres] version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

Possibly related PRs

• OpenDIKW/dikw-core#109: Same ARG DIKW_VERSION bump in the same Dockerfile.
• OpenDIKW/dikw-core#113: Same ARG DIKW_VERSION bump in the same Dockerfile.
• OpenDIKW/dikw-core#119: Same ARG DIKW_VERSION bump in the same Dockerfile, also adds CI automation to keep the arg in sync.

Poem

🐇 A number so small, just a patch on the vine,
From four to five, the version does climb.
The Docker file hums, pip installs anew,
dikw-core fresh with a version that's true.
Hop hop, little bump, the build carries on! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the Dockerfile version bump to DIKW_VERSION v0.6.5, matching the main change.
Description check	✅ Passed	The description explains the release/PyPI motivation and CI behavior, but it omits the template's explicit test plan checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/docker-version-v0.6.5

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!