wehub-resource-sync
161ef94b4f
Check engine pin consistency / Dockerfile / CI pin consistency (push) Successful in 8s
Sirius CI/CD Pipeline / Detect Changes (push) Successful in 23s
Validate Docker Configuration / Validate Docker Compose Configuration (push) Successful in 47s
Sirius CI/CD Pipeline / Build API (${{ matrix.platform }}) (push) Has been cancelled
Sirius CI/CD Pipeline / Build UI (${{ matrix.platform }}) (push) Has been cancelled
Sirius CI/CD Pipeline / Merge Engine Manifest (push) Has been cancelled
Sirius CI/CD Pipeline / Merge API Manifest (push) Has been cancelled
Sirius CI/CD Pipeline / Merge UI Manifest (push) Has been cancelled
Sirius CI/CD Pipeline / Build Engine (${{ matrix.platform }}) (push) Has been cancelled
Sirius CI/CD Pipeline / Build Infra (${{ matrix.service }}, ${{ matrix.platform }}) (push) Has been cancelled
Sirius CI/CD Pipeline / Merge Infra Manifest (sirius-postgres) (push) Has been cancelled
Sirius CI/CD Pipeline / Merge Infra Manifest (sirius-rabbitmq) (push) Has been cancelled
Sirius CI/CD Pipeline / Merge Infra Manifest (sirius-valkey) (push) Has been cancelled
Sirius CI/CD Pipeline / Integration Test (push) Has been cancelled
Sirius CI/CD Pipeline / Public Stack Contract (push) Has been cancelled
Sirius CI/CD Pipeline / Dispatch Demo Deployment (sirius-demo branch) (push) Has been cancelled
Sirius CI/CD Pipeline / Dispatch Demo Canary (main branch) (push) Has been cancelled
Sirius CI/CD Pipeline / Guard Registry Namespace (push) Has been cancelled
1.2 KiB
1.2 KiB
Summary
Describe the problem this PR solves and why this approach was chosen.
Change Type
- Bug fix
- Feature
- Refactor
- Documentation
- CI/CD or automation
- Security hardening
Scope
sirius-uisirius-apisirius-engine- Infrastructure (
postgres,rabbitmq,valkey, compose) - Documentation
- Other (describe below)
Related Issue
Closes #
Validation
- I ran required local validation for this change
- I attached logs, screenshots, or output where relevant
- I tested failure paths or edge cases where applicable
- CI checks are expected to pass for this PR
Security and Risk Review
- No security impact
- Security impact reviewed and documented
- Rollback steps are documented for risky operational changes
Documentation
- No docs change needed
- Updated
README.md,CONTRIBUTING.md,SECURITY.md, or related docs - Added/updated issue templates or workflow docs
Deployment Notes
List any operational notes (migrations, secret changes, compose changes, required order of deployment, etc.).
Additional Context
Add anything reviewers should know (tradeoffs, follow-ups, known limitations).