chore(deps): bump pgvector/pgvector from 0.8.6-pg15 to 0.8.7-pg15 in /compose/production/postgres

[dependabot]

Bumps pgvector/pgvector from 0.8.6-pg15 to 0.8.7-pg15.

[claude]

Review: one-line patch bump of the production Postgres base image (pgvector 0.8.6-pg15 → 0.8.7-pg15). Same PG major, so no data-directory compatibility concern, and no code, security or test changes.

Notes:

• The image only changes the extension's available version. Existing databases keep the old extension until ALTER EXTENSION vector UPDATE; is run. After deploying, check SELECT extversion FROM pg_extension WHERE extname='vector'; and update if desired. Patch releases are normally drop-in, but if you have HNSW indexes, take a backup first.
• Check that the local/test compose files use a matching pgvector version, so dev and test don't drift from production.

LGTM once CI is green.

[JSv4]

@dependabot rebase

[claude]

Review: one-line Dependabot bump of the production Postgres image (pgvector 0.8.6 → 0.8.7, same pg15 base). It's the only pgvector/pgvector reference in the repo, so no other files need to change.

• Compatibility: this is a patch release of the extension. It doesn't change the Postgres major version or the on-disk format. Migration 0063 and init.sql don't depend on a specific pgvector version.
• Existing databases: the image only ships the extension binaries. Existing databases keep the old extension version until ALTER EXTENSION vector UPDATE runs. That isn't required for the bump, but it's worth running if you want the 0.8.7 fixes on current deployments.
• Tests: none are needed for this change. I'd confirm CI, including any test that exercises HNSW or vector search, is green before merging.
• Changelog: a changelog.d fragment is optional for a dependency bump.

LGTM.