[dependabot]

Warning

Cooldown could not be applied because no publication date was available from the registry.

Bumps the infra-base-images group with 3 updates in the /src/agent_env/env/envs/service_db directory: docker/library/postgres, docker/library/python and sosedoff/pgweb.
Bumps the infra-base-images group with 1 update in the /src/agent_env/env/envs/website_browser directory: docker/library/node.

Updates docker/library/postgres from 16-alpine to 18-alpine

Updates docker/library/python from 3.12-slim-bookworm to 3.15-slim-bookworm

Updates sosedoff/pgweb from 0.16.2 to 0.17.0

Updates docker/library/node from 22-slim to 26-slim

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Confidence Score: 3/5

Fix the Python stage mismatch and PostgreSQL snapshot path before merging.

Findings

1.  Database tools cannot start ▶
2.  Database snapshots stop working ▶

Fix with agent prompt

### Issue 1
src/agent_env/env/envs/service_db/Dockerfile.db-mcp:27
`Dockerfile.db-mcp` still builds `/app/.venv` with Python 3.12, but now copies it into a Python 3.15 image. The copied environment depends on the builder's Python 3.12 interpreter and packages. Copying `/app` does not install that interpreter in the final image, so `postgres-mcp` cannot start.

Keep both stages on the same Python version, or rebuild the environment for the new runtime.

### Issue 2
src/agent_env/env/envs/service_db/Dockerfile:1
PostgreSQL 18 uses `/var/lib/postgresql/18/docker` as its default `PGDATA`, but `_snapshot_servicedb` still copies `/var/lib/postgresql/data`. Snapshot creation therefore cannot export the database.

That function also builds snapshots on PostgreSQL 16, which cannot read PostgreSQL 18 data files even after the copy path is fixed. Update snapshot capture and its base image together, or retain PostgreSQL 16.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Updates four pinned base images: PostgreSQL, Python, pgweb, and Node.

• The service database containers use newer pinned images.
• The website browser runs on a newer pinned Node image.

_{Reviews (1) · Last reviewed commit: "build(deps): bump the infra-base-images ..." · Reviewed by Greptile}

[greptile-apps]

Database tools cannot start

Dockerfile.db-mcp still builds /app/.venv with Python 3.12, but now copies it into a Python 3.15 image. The copied environment depends on the builder's Python 3.12 interpreter and packages. Copying /app does not install that interpreter in the final image, so postgres-mcp cannot start.

Keep both stages on the same Python version, or rebuild the environment for the new runtime.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/agent_env/env/envs/service_db/Dockerfile.db-mcp
Line: 27

Comment:
**Database tools cannot start**

`Dockerfile.db-mcp` still builds `/app/.venv` with Python 3.12, but now copies it into a Python 3.15 image. The copied environment depends on the builder's Python 3.12 interpreter and packages. Copying `/app` does not install that interpreter in the final image, so `postgres-mcp` cannot start.

Keep both stages on the same Python version, or rebuild the environment for the new runtime.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Database snapshots stop working

PostgreSQL 18 uses /var/lib/postgresql/18/docker as its default PGDATA, but _snapshot_servicedb still copies /var/lib/postgresql/data. Snapshot creation therefore cannot export the database.

That function also builds snapshots on PostgreSQL 16, which cannot read PostgreSQL 18 data files even after the copy path is fixed. Update snapshot capture and its base image together, or retain PostgreSQL 16.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/agent_env/env/envs/service_db/Dockerfile
Line: 1

Comment:
**Database snapshots stop working**

PostgreSQL 18 uses `/var/lib/postgresql/18/docker` as its default `PGDATA`, but `_snapshot_servicedb` still copies `/var/lib/postgresql/data`. Snapshot creation therefore cannot export the database.

That function also builds snapshots on PostgreSQL 16, which cannot read PostgreSQL 18 data files even after the copy path is fixed. Update snapshot capture and its base image together, or retain PostgreSQL 16.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.