recipe-maintainers/bluesky-pds
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore: upgrade to 0.3.0+v0.4.219 #2

Open
autonomic-bot wants to merge 1 commits from upgrade-0.3.0+v0.4.219 into main
pull from: upgrade-0.3.0+v0.4.219
merge into: recipe-maintainers:main
Conversation 6 Commits 1 Files Changed 1 +2 -2
autonomic-bot commented 2026-06-11 11:38:08 +00:00
Owner
Copy Link

What

Re-pin the app image from the moving tag ghcr.io/bluesky-social/pds:0.4 to the exact released tag 0.4.219, and bump the version label 0.2.0+v0.4 → 0.3.0+v0.4.219. Two-line diff; entrypoint.sh.tmpl is intentionally unchanged.

Why

The recipe currently cannot deploy at all: the app container crash-loops Error: Cannot find module '/app/index.js' (MODULE_NOT_FOUND).

Root cause: :0.4 is a moving tag that upstream now republishes with main-branch builds. As of 2026-05-30 it is identical to latest and contains @atproto/pds 0.5.1 on Node v24.15.0, with the service restructured to run TypeScript directly (/app/index.ts, CMD node --enable-source-maps index.ts — there is no index.js anymore). This recipe overrides the image entrypoint with a script that ends exec node --enable-source-maps index.js, which can no longer resolve.

0.4.219 is the newest released exact tag (upstream publishes git tags, no GitHub Releases) and keeps the layout this recipe expects: Node 20.20, /app/index.js, dumb-init, image CMD identical to the entrypoint's exec line. The recipe's env/secret interface (PDS_HOSTNAME, PDS_JWT_SECRET, PDS_ADMIN_PASSWORD, PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX, …) is unchanged across the 0.4.x line.

Evidence (reproducible):

  • docker run --rm --entrypoint sh ghcr.io/bluesky-social/pds:0.4 -c 'node --version; ls /app' → v24.15.0, index.ts … (no index.js)
  • docker run --rm --entrypoint sh ghcr.io/bluesky-social/pds:0.4.219 -c 'node --version; ls /app' → v20.20.2, index.js …
  • Upstream Dockerfile@main: node:24.15-alpine3.23, CMD ["node", "--enable-source-maps", "index.ts"]; Dockerfile@v0.4.219: node:20.20-alpine3.23, CMD ["node", "--enable-source-maps", "index.js"]

When upstream cuts real 0.5.x release tags, a follow-up upgrade should migrate the entrypoint to index.ts alongside that bump. Until then, exact-tag pinning prevents this class of breakage.

Fix authored by the cc-ci loop agents; verified via recipe CI on this PR (!testme).

## What Re-pin the app image from the moving tag `ghcr.io/bluesky-social/pds:0.4` to the exact released tag `0.4.219`, and bump the version label `0.2.0+v0.4` → `0.3.0+v0.4.219`. Two-line diff; `entrypoint.sh.tmpl` is intentionally unchanged. ## Why The recipe currently cannot deploy at all: the app container crash-loops `Error: Cannot find module '/app/index.js'` (MODULE_NOT_FOUND). Root cause: `:0.4` is a **moving tag that upstream now republishes with main-branch builds**. As of 2026-05-30 it is identical to `latest` and contains `@atproto/pds` **0.5.1** on Node v24.15.0, with the service restructured to run TypeScript directly (`/app/index.ts`, `CMD node --enable-source-maps index.ts` — there is **no `index.js`** anymore). This recipe overrides the image entrypoint with a script that ends `exec node --enable-source-maps index.js`, which can no longer resolve. `0.4.219` is the newest released exact tag (upstream publishes git tags, no GitHub Releases) and keeps the layout this recipe expects: Node 20.20, `/app/index.js`, `dumb-init`, image CMD identical to the entrypoint's exec line. The recipe's env/secret interface (PDS_HOSTNAME, PDS_JWT_SECRET, PDS_ADMIN_PASSWORD, PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX, …) is unchanged across the 0.4.x line. Evidence (reproducible): - `docker run --rm --entrypoint sh ghcr.io/bluesky-social/pds:0.4 -c 'node --version; ls /app'` → `v24.15.0`, `index.ts …` (no index.js) - `docker run --rm --entrypoint sh ghcr.io/bluesky-social/pds:0.4.219 -c 'node --version; ls /app'` → `v20.20.2`, `index.js …` - Upstream Dockerfile@main: `node:24.15-alpine3.23`, `CMD ["node", "--enable-source-maps", "index.ts"]`; Dockerfile@v0.4.219: `node:20.20-alpine3.23`, `CMD ["node", "--enable-source-maps", "index.js"]` When upstream cuts real 0.5.x release tags, a follow-up upgrade should migrate the entrypoint to `index.ts` alongside that bump. Until then, exact-tag pinning prevents this class of breakage. --- Fix authored by the cc-ci loop agents; verified via recipe CI on this PR (`!testme`).
autonomic-bot added 1 commit 2026-06-11 11:38:09 +00:00
chore: upgrade to 0.3.0+v0.4.219
All checks were successful
cc-ci/testme cc-ci: success
Details
f7b6c8dfb8 
Pin an exact released image tag. The previous pin :0.4 is a moving tag
that upstream now republishes with main-branch builds (currently
@atproto/pds 0.5.1 on Node 24, where the service entrypoint moved from
/app/index.js to /app/index.ts), so the recipe's entrypoint.sh
(exec node --enable-source-maps index.js) crash-loops MODULE_NOT_FOUND.
ghcr.io/bluesky-social/pds:0.4.219 is the newest released exact tag and
keeps the layout this recipe's entrypoint expects (Node 20.20,
/app/index.js, dumb-init).
autonomic-bot commented 2026-06-11 11:38:18 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-11 11:38:48 +00:00
Author
Owner
Copy Link

🌻 cc-ci — bluesky-pds @ f7b6c8df ❌ failure

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `bluesky-pds` @ `f7b6c8df` ❌ **failure** [![cc-ci result card](https://ci.commoninternet.net/runs/423/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/423) [![level](https://ci.commoninternet.net/runs/423/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/423) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/423) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-06-11 11:51:29 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-11 11:51:56 +00:00
Author
Owner
Copy Link

🌻 cc-ci — bluesky-pds @ f7b6c8df ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `bluesky-pds` @ `f7b6c8df` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/427/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/427) [![level](https://ci.commoninternet.net/runs/427/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/427) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/427) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-06-11 15:46:21 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-11 15:46:52 +00:00
Author
Owner
Copy Link

🌻 cc-ci — bluesky-pds @ f7b6c8df ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `bluesky-pds` @ `f7b6c8df` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/435/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/435) [![level](https://ci.commoninternet.net/runs/435/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/435) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/435) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-0.3.0+v0.4.219:upgrade-0.3.0+v0.4.219
git checkout upgrade-0.3.0+v0.4.219
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/bluesky-pds#2
No description provided.
Delete Branch "upgrade-0.3.0+v0.4.219"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?