Updating

DrupalClaw uses semantic versioning. Images are published to GHCR with version tags (1.4.3, 1.4) and latest. Release notes are on the Releases page.

Update to the latest version

cd docker
docker compose pull
docker compose up -d

Always run docker compose pull first. The compose file defines both an image: and a build:. Without a pull, docker compose up reuses any image you already have locally under the same tag, so you can keep running an old version without noticing.

Your data is safe: the Drupal project, chat history, flows, plans and provider credentials live in Docker volumes and are not touched by an image update.

Pin a version

Edit docker/docker-compose.yml:

image: ghcr.io/paulocarv/drupalclaw-project:1.4.3

How skills are updated

When the container starts, built-in skills are copied into /workspace/.pi/skills/:

• New skills in the image are added automatically
• Skills you already have are never overwritten, so your edits are safe. This also means an updated version of an existing skill does not reach an existing workspace by itself

To get the current version of a built-in skill, delete its folder from /workspace/.pi/skills/ and restart the container (docker compose restart). It is copied again from the image. Skills copied this way come from /opt/drupalclaw/skills inside the image (v1.4.3 and later).

Related

• Providers and Login