sax3l/c0py
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(api): Postgres persistence for registries + scans #2

Closed
admin wants to merge 0 commits from feat/persistence into main
pull from: feat/persistence
merge into: sax3l:main
Conversation 0 Commits - Files Changed -
admin commented 2026-09-16 20:32:50 +00:00
Owner
Copy Link
Copy Source

Landad som merge 26df793 (CI grön 3/3 på PR).

Landad som merge `26df793` (CI grön 3/3 på PR).
admin added 1 commit 2026-09-16 20:32:51 +00:00
feat(api): Postgres persistence for registries + scans (owner-scoped, fail-closed)
CI (SIAX Cloud) / security (push) Successful in 13s
Details
CI (SIAX Cloud) / contracts (pull_request) Successful in 17s
Details
CI (SIAX Cloud) / security (pull_request) Successful in 13s
Details
CI (SIAX Cloud) / contracts (push) Successful in 16s
Details
CI (SIAX Cloud) / quality (push) Successful in 52s
Details
CI (SIAX Cloud) / quality (pull_request) Successful in 1m13s
Details
9482a97795 
- schema migration 001 (registries, scans; owner_sub = introspected subject)
- pg pool + services; scan ownership enforced in SQL (INSERT ... SELECT WHERE owner_sub)
- real handlers: 201/400/404/500, owner-scoped GET/POST, listScans registryId filter
- graceful shutdown closes pool; 7 new persistence tests (21/21)
admin closed this pull request 2026-09-16 20:35:30 +00:00
All checks were successful
CI (SIAX Cloud) / security (push) Successful in 13s
Details
CI (SIAX Cloud) / contracts (pull_request) Successful in 17s
Required
Details
CI (SIAX Cloud) / security (pull_request) Successful in 13s
Required
Details
CI (SIAX Cloud) / contracts (push) Successful in 16s
Details
CI (SIAX Cloud) / quality (push) Successful in 52s
Details
CI (SIAX Cloud) / quality (pull_request) Successful in 1m13s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
P0-critical
Drop-everything: active exploit path, live credential exposure, or data-loss risk
 P1-high
Real risk or blocker, not actively burning, should not wait long
 P2-normal
Real but not urgent
 auto-verified
Confirmed by actually running code/tests, not by reading a claim
 blocked
Blocked on another issue/PR/external dependency
 needs-simon
Cannot proceed without Simon's decision or an action only he can take
 ready-for-review
A PR already exists and is waiting on human review/merge decision
 type:data-integrity
Duplicate truth, drift, unverified claim, migration correctness
 type:governance
Process, ownership, incident-response, review-flow
 type:infra
Server/deploy/CI/branch-protection/infrastructure config
 type:product-decision
Needs a business/architecture call only Simon can make
 type:security
Vulnerability, auth gap, credential handling
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin (Simon Axelsson) siax-bot siax-healer (siax-healer (CI self-healing agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sax3l/c0py#2
Delete Branch "feat/persistence"

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?