deploy: staging pins for 41b51ac3 (images.yml GH013) - #257
Conversation
|
@greptileai review |
Greptile SummaryThis PR updates staging deployment metadata to reference immutable container digests for source commit Confidence Score: 5/5Safe to merge. There are no outstanding findings. Files Needing Attention: None. Reviews (9): Last reviewed commit: "Merge branch 'main' into cursor/staging-..." | Re-trigger Greptile |
87582e3 to
53bdba7
Compare
|
@greptileai review Retargeted to |
53bdba7 to
b9a0a69
Compare
|
@greptileai review Retargeted to |
b9a0a69 to
c8228ca
Compare
|
@greptileai review Retargeted to |
c8228ca to
3abe69c
Compare
|
@greptileai review Retargeted to |
3abe69c to
d3ff5f5
Compare
|
@greptileai review Retargeted to |
d3ff5f5 to
fbc6f43
Compare
|
@greptileai review Retargeted to |
fbc6f43 to
529d50f
Compare
|
@greptileai review Retargeted to |
Why
images.ymlonmainbuilt GHCR digests for41b51ac3(#266) then update · commit staging pins failed with GH013. Run 34469793971.Staging on
mainis stilla8b90181(from #245). Prod pins were not touched.What changed
deploy/digests/41b51ac384e25234d4c5612cbdc2535ca4ad1524.jsondeploy/pins/staging.jsoncommit_sha→41b51ac3…previousis the completea8b90181current set41b51ac3)a8b90181)sha256:0651f5bb…sha256:650bfe48…sha256:ed23e598…sha256:17ded01b…sha256:a5c24564…sha256:e42a763e…sha256:c0a70275…sha256:cdc9696f…sha256:18753a0d…sha256:b7a33f89…This does not bump
config/proof-pin.toml. Merging this pin commit will GH013 once more (pin-commit loop); that is expected.Other
mainreds (not this PR)base-hostsHTTP 422must have no more than 50 rules. Ops prune leftover ephemeral/32SSH rules.metadata/testnet.lockdrift. Deliberate lock refresh after reviewing chain changes; do not invent.Greptile
529d50f3)@greptileai reviewTest plan
staging.jsoncommit_sha==41b51ac3…previousis the fulla8b90181service setprod.jsonunchangeddeploy-stagingcan match staging pins to this SHARisk
Staging pin ladder only. No emission, no
BASE_*rename, no invented sha256.Naming
I did not rename
BASE_*environment variables, deployed host paths, GHCR package names, orbase-*-v1cryptographic domain tags.