Bump the app image to the newest available bluesky-social/pds tag. abra recipe upgrade bluesky-pds -m reports candidates ["0.4.5037","0.4.5036","0.4.5034"];
this takes the newest, 0.4.5037. caddy is unchanged (abra confirms 2 is latest).
service
image
current
new
app
ghcr.io/bluesky-social/pds
0.4.5027
0.4.5037
caddy
caddy
2
2 (unchanged)
Image-tag mapping: 0.4.5NNN == @atproto/pds0.5.NN, so this step is @atproto/pds0.5.36 → 0.5.37 (cumulative 0.5.27 → 0.5.37).
None. Every release in the window (@atproto/pds 0.5.27 → 0.5.37) is a non-breaking patch:
the recipe's env interface is unchanged (same PDS_* set + the same three secrets), no data
migration is required, and the health endpoint GET /xrpc/_health is unchanged. Notable
upstream items: since/startCursor added to getTimeline/getListFeed, improved actor-store
resource management, and MSTs referencing the same node are now rejected (VisitedCidError; importRepo → InvalidRequest).
Advisory scan
Deterministic scanner (cc-ci-plan/advisory-scan.py bluesky-pds --from 0.4.5027 --to 0.4.5037): 0 CVEs fixed by this upgrade; 15 advisories seen but not version-classified (they belong to
other images / fall outside this window). --adjudicate produced no open cases, and the
release-note read found no CVEs either. Union count: 0.
Verification
abra recipe lint bluesky-pds -C -n: only pre-existing warnings (R002 healthcheck, R007
README metadata, R015 secret-name length), unrelated to this bump.
Direct --chaos deploy on cc-ci (dev-bluesky-pds.ci.commoninternet.net, --server default)
performed a live deploy of the new tag: converged 1/1 on ghcr.io/bluesky-social/pds:0.4.5037; logs starting→started; public GET /xrpc/_health returned {"version":"0.4.5037"} (HTTP 200). The dev deploy was torn down
afterwards (no stack, volumes, or secrets left behind).
!testme results are posted below.
Release
This PR deliberately does not bump the coop-cloud.${STACK_NAME}.version label. After
merge, the operator runs:
abra recipe release bluesky-pds -z
(no --dry-run; -z patch — a non-breaking upstream patch bump). The recipe version bump +
tag + publish are the operator's final step.
## Upgrade: bluesky-pds app `0.4.5027` → `0.4.5037`
Bump the `app` image to the newest available `bluesky-social/pds` tag.
`abra recipe upgrade bluesky-pds -m` reports candidates `["0.4.5037","0.4.5036","0.4.5034"]`;
this takes the newest, `0.4.5037`. `caddy` is unchanged (abra confirms `2` is latest).
| service | image | current | new |
|---------|-------|---------|-----|
| app | `ghcr.io/bluesky-social/pds` | `0.4.5027` | `0.4.5037` |
| caddy | `caddy` | `2` | `2` (unchanged) |
Image-tag mapping: `0.4.5NNN` == `@atproto/pds` `0.5.NN`, so this step is
`@atproto/pds` **0.5.36 → 0.5.37** (cumulative **0.5.27 → 0.5.37**).
**Upstream release notes:** app 0.4.5027→0.4.5037 (`@atproto/pds` 0.5.27→0.5.37):
https://github.com/bluesky-social/atproto/blob/main/packages/pds/CHANGELOG.md
### Operator Action Required
None. Every release in the window (`@atproto/pds` 0.5.27 → 0.5.37) is a non-breaking patch:
the recipe's env interface is unchanged (same `PDS_*` set + the same three secrets), no data
migration is required, and the health endpoint `GET /xrpc/_health` is unchanged. Notable
upstream items: `since`/`startCursor` added to `getTimeline`/`getListFeed`, improved actor-store
resource management, and MSTs referencing the same node are now rejected (`VisitedCidError`;
`importRepo` → `InvalidRequest`).
### Advisory scan
Deterministic scanner (`cc-ci-plan/advisory-scan.py bluesky-pds --from 0.4.5027 --to 0.4.5037`):
**0 CVEs fixed by this upgrade**; 15 advisories seen but not version-classified (they belong to
other images / fall outside this window). `--adjudicate` produced no open cases, and the
release-note read found no CVEs either. Union count: **0**.
### Verification
- `abra recipe lint bluesky-pds -C -n`: only pre-existing warnings (R002 healthcheck, R007
README metadata, R015 secret-name length), unrelated to this bump.
- Direct `--chaos` deploy on cc-ci (`dev-bluesky-pds.ci.commoninternet.net`, `--server default`)
performed a live deploy of the new tag: converged `1/1` on
`ghcr.io/bluesky-social/pds:0.4.5037`; logs `starting`→`started`; public
`GET /xrpc/_health` returned `{"version":"0.4.5037"}` (HTTP 200). The dev deploy was torn down
afterwards (no stack, volumes, or secrets left behind).
- `!testme` results are posted below.
### Release
This PR deliberately does **not** bump the `coop-cloud.${STACK_NAME}.version` label. After
merge, the operator runs:
abra recipe release bluesky-pds -z
(no `--dry-run`; `-z` patch — a non-breaking upstream patch bump). The recipe version bump +
tag + publish are the operator's final step.
NOT merged — for operator review.
cc @trav @notplants
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Upgrade: bluesky-pds app
0.4.5027→0.4.5037Bump the
appimage to the newest availablebluesky-social/pdstag.abra recipe upgrade bluesky-pds -mreports candidates["0.4.5037","0.4.5036","0.4.5034"];this takes the newest,
0.4.5037.caddyis unchanged (abra confirms2is latest).ghcr.io/bluesky-social/pds0.4.50270.4.5037caddy22(unchanged)Image-tag mapping:
0.4.5NNN==@atproto/pds0.5.NN, so this step is@atproto/pds0.5.36 → 0.5.37 (cumulative 0.5.27 → 0.5.37).Upstream release notes: app 0.4.5027→0.4.5037 (
@atproto/pds0.5.27→0.5.37):https://github.com/bluesky-social/atproto/blob/main/packages/pds/CHANGELOG.md
Operator Action Required
None. Every release in the window (
@atproto/pds0.5.27 → 0.5.37) is a non-breaking patch:the recipe's env interface is unchanged (same
PDS_*set + the same three secrets), no datamigration is required, and the health endpoint
GET /xrpc/_healthis unchanged. Notableupstream items:
since/startCursoradded togetTimeline/getListFeed, improved actor-storeresource management, and MSTs referencing the same node are now rejected (
VisitedCidError;importRepo→InvalidRequest).Advisory scan
Deterministic scanner (
cc-ci-plan/advisory-scan.py bluesky-pds --from 0.4.5027 --to 0.4.5037):0 CVEs fixed by this upgrade; 15 advisories seen but not version-classified (they belong to
other images / fall outside this window).
--adjudicateproduced no open cases, and therelease-note read found no CVEs either. Union count: 0.
Verification
abra recipe lint bluesky-pds -C -n: only pre-existing warnings (R002 healthcheck, R007README metadata, R015 secret-name length), unrelated to this bump.
--chaosdeploy on cc-ci (dev-bluesky-pds.ci.commoninternet.net,--server default)performed a live deploy of the new tag: converged
1/1onghcr.io/bluesky-social/pds:0.4.5037; logsstarting→started; publicGET /xrpc/_healthreturned{"version":"0.4.5037"}(HTTP 200). The dev deploy was torn downafterwards (no stack, volumes, or secrets left behind).
!testmeresults are posted below.Release
This PR deliberately does not bump the
coop-cloud.${STACK_NAME}.versionlabel. Aftermerge, the operator runs:
(no
--dry-run;-zpatch — a non-breaking upstream patch bump). The recipe version bump +tag + publish are the operator's final step.
NOT merged — for operator review.
cc @trav @notplants
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
bluesky-pds@589d490b✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
bluesky-pds@589d490b✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
bluesky-pds@589d490b✅ passedfull logs · dashboard
chore: upgrade app to 0.4.5034to chore: upgrade bluesky-social/pds to 0.4.5034!testme
🌻 cc-ci —
bluesky-pds@589d490b✅ passedfull logs · dashboard
chore: upgrade bluesky-social/pds to 0.4.5034to chore: upgrade app to 0.4.5036!testme
🌻 cc-ci —
bluesky-pds@1a51596f✅ passedfull logs · dashboard
chore: upgrade app to 0.4.5036to chore: upgrade app to 0.4.5037!testme
🌻 cc-ci —
bluesky-pds@7ed391b9✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
bluesky-pds@7ed391b9✅ passedfull logs · dashboard
autonomic-bot referenced this pull request2026-10-23 02:24:53 +00:00
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.