groombook/api
13
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Promote dev → uat: provenance: false CI fix #65

Merged
The Dogfather merged 3 commits from dev into uat 2026-05-23 01:41:00 +00:00
Conversation 0 Commits 3 Files Changed 1
+6
The Dogfather commented 2026-05-23 01:40:21 +00:00
Member
Copy Link
Copy Source

Summary

Promotes dev to uat after merging PR #64 — adds provenance: false to all four docker/build-push-action@v6 steps in CI.

Changes included

  • fix(GRO-1576): add provenance: false to all build-push-action steps (API, migrate, seed, reset)

Parent: GRO-1575

## Summary Promotes dev to uat after merging PR #64 — adds `provenance: false` to all four `docker/build-push-action@v6` steps in CI. ## Changes included - fix(GRO-1576): add `provenance: false` to all build-push-action steps (API, migrate, seed, reset) Parent: GRO-1575
The Dogfather added 3 commits 2026-05-23 01:40:21 +00:00
fix: add network=host to buildx driver-opts for DinD DNS resolution
CI / Test (push) Successful in 43s
Details
CI / Lint & Typecheck (push) Successful in 44s
Details
CI / Build & Push Docker Images (push) Failing after 39s
Details
4e8c66f3ca 
Co-Authored-By: Paperclip <noreply@paperclip.ing>
fix(GRO-1576): add provenance: false to all build-push-action steps
CI / Lint & Typecheck (pull_request) Successful in 11s
Details
CI / Test (pull_request) Successful in 11s
Details
CI / Build & Push Docker Images (pull_request) Failing after 2m28s
Details
e26d960046 
Docker Buildx v6 defaults to OCI attestation manifests (--attest
type=provenance,mode=max). These hit a Gitea registry bug when image
layers are pre-existing (blob mount), causing "unknown" errors on manifest
list push. API image succeeds because it pushes new layers; migrate/seed/
reset fail because their layers already exist.

Disabling provenance attestation on all four build-push-action steps
resolves the push failures. Addresses GRO-1575.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Merge pull request 'fix(GRO-1576): add provenance: false to all build-push-action steps' (#64) from fix/gro-1576-ci-provenance-false into dev
CI / Lint & Typecheck (push) Successful in 10s
Details
CI / Test (push) Successful in 11s
Details
CI / Build & Push Docker Images (push) Successful in 20s
Details
33aa63b10f 
fix(GRO-1576): add provenance: false to all build-push-action steps (#64)

Disables OCI attestation manifest generation that was hitting a Gitea registry bug when image layers are pre-existing.

Reviewed-by: Lint Roller (QA)
Approved-by: The Dogfather (CTO)
The Dogfather merged commit 2380698128 into uat 2026-05-23 01:41:00 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/api#65
Delete Branch "dev"

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?