Jinemi/thermograph
4
0
Fork 0
Code Issues 2 Pull requests 9 Projects Releases Packages Wiki Activity Actions 1

Finish the domain-sha tag keying: three deploy workflows were missed #6

Merged
admin_emi merged 1 commit from domain-sha-tags-remainder into dev 2026-07-23 13:58:59 +00:00
Conversation 0 Commits 1 Files changed 3 +39 -9
admin_emi commented 2026-07-23 13:58:15 +00:00
Owner
Copy link

The first pass's patch loop aborted partway, leaving frontend-deploy, backend-deploy-prod, and frontend-deploy-prod on GITHUB_SHA keys — the cause of the re-proof failures (they chased images tagged with promotion-merge tips). Same fix, per-file verified this time.

The first pass's patch loop aborted partway, leaving frontend-deploy, backend-deploy-prod, and frontend-deploy-prod on GITHUB_SHA keys — the cause of the re-proof failures (they chased images tagged with promotion-merge tips). Same fix, per-file verified this time.
admin_emi added 1 commit 2026-07-23 13:58:16 +00:00
Finish the domain-sha tag keying: three deploy workflows were missed
All checks were successful
PR build (required check) / changes (pull_request) Successful in 6s
Details
secrets-guard / encrypted (pull_request) Successful in 5s
Details
PR build (required check) / build-backend (pull_request) Has been skipped
Details
PR build (required check) / build-frontend (pull_request) Has been skipped
Details
PR build (required check) / validate-observability (pull_request) Has been skipped
Details
PR build (required check) / gate (pull_request) Successful in 2s
Details
94595dcad1 
The previous pass's patch loop aborted on an assertion partway through,
leaving frontend-deploy, backend-deploy-prod, and frontend-deploy-prod
still keying on GITHUB_SHA -- which is why their re-proof dispatches went
looking for images tagged with promotion-merge tips. Same fix as the
rest: full-depth checkout + git log -1 -- <domain>/.
admin_emi merged commit af839c6cd0 into dev 2026-07-23 13:58:59 +00:00
admin_emi deleted branch domain-sha-tags-remainder 2026-07-23 13:59:00 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Jinemi/thermograph#6
No description provided.
Delete branch "domain-sha-tags-remainder"

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?