AP: Tag specific version along with migrate

- AP migration should be tagged along with the main AP instance to keep things in line
  - Renovate will now group them together so it bumps them at the same time in the same PR/commit etc to keep things aligned
- Moving to specific version pinning as well to make the renovate diffs clearer
This commit is contained in:
James Loh
2025-07-14 12:31:49 +10:00
committed by James Loh
parent 615b60fbb8
commit d06485b4d4
2 changed files with 14 additions and 2 deletions

View File

@@ -9,6 +9,18 @@
],
suppressNotifications: ["prIgnoreNotification"],
packageRules: [
{
description: "Group ActivityPub containers together",
matchDatasources: ["docker", "github-tags", "docker-compose"],
matchPackageNames: [
"ghcr.io/tryghost/activitypub",
"ghcr.io/tryghost/activitypub-migrations",
],
groupName: "ActivityPub",
groupSlug: "activitypub",
additionalBranchPrefix: "",
separateMinorPatch: false,
},
{
description: "Auto-merge initial digest pinning",
matchDatasources: ["docker", "github-tags"],

View File

@@ -96,7 +96,7 @@ services:
- ghost_network
activitypub:
image: ghcr.io/tryghost/activitypub:1
image: ghcr.io/tryghost/activitypub:1.0.1
restart: always
expose:
- "8080"
@@ -180,7 +180,7 @@ services:
tty: true
activitypub-migrate:
image: ghcr.io/tryghost/activitypub-migrations:edge
image: ghcr.io/tryghost/activitypub-migrations:1.0.1
environment:
MYSQL_DB: mysql://${DATABASE_USER:-ghost}:${DATABASE_PASSWORD:?DATABASE_PASSWORD environment variable is required}@tcp(db:3306)/activitypub
networks: