Bump pgvector/pgvector from 0.8.4-pg15 to 0.8.5-pg15 in /compose/production/postgres

[dependabot]

Bumps pgvector/pgvector from 0.8.4-pg15 to 0.8.5-pg15.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[claude]

Review

This is a minor patch-version bump (pgvector/pgvector:0.8.4-pg15 → 0.8.5-pg15) generated by Dependabot, touching a single line in compose/production/postgres/Dockerfile.

Findings:

• No code quality, correctness, or security concerns — this is a base image version bump only.
• Verified compose/production/postgres/Dockerfile is the single source of truth for the postgres image (referenced via dockerfile: in both local.yml and test.yml), so local/test/production environments all stay in sync automatically — no other files need updating.
• 0.8.4 → 0.8.5 is a patch release of pgvector; per the upstream changelog this is a bug-fix release with no breaking changes to the extension API, index formats, or SQL functions, so no migration or init.sql changes are needed.
• The repo's init.sql / migration 0063 HNSW settings referenced in the file's header comment are unaffected by this bump.

Test coverage: No test changes needed for a base image patch bump. Standard CI (image build + test suite against the new image) is sufficient verification.

Looks safe to merge.