SLP_Software/slp-modular-cms
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity
83 Commits 1 Branch 0 Tags
92547efd4705783284746b044a326d1cc312d6f8
Commit Graph
2 Commits
Author SHA1 Message Date
SluijsensandClaude Sonnet 5 92547efd47 Allows deploy-test to run on pull_request events too
Continuous Integration / config (pull_request) Canceled after 0s
Details
Continuous Integration / backend-build (pull_request) Canceled after 0s
Details
Continuous Integration / backend-test (pull_request) Canceled after 0s
Details
Continuous Integration / vulnerability-scan (pull_request) Canceled after 0s
Details
Continuous Integration / frontend-prepare (pull_request) Canceled after 0s
Details
Continuous Integration / frontend-build (pull_request) Canceled after 0s
Details
Continuous Integration / frontend-test (pull_request) Canceled after 0s
Details
Continuous Integration / frontend-lint (pull_request) Canceled after 0s
Details
Continuous Integration / publish-test (pull_request) Canceled after 0s
Details
Continuous Integration / publish-production (pull_request) Canceled after 0s
Details
Continuous Integration / deploy-test (pull_request) Canceled after 0s
Details
Continuous Integration / deploy-production (pull_request) Canceled after 0s
Details 
So PR pushes deploy straight to the test environment, without a manual
workflow_dispatch each time. Only one test environment exists, so this
means concurrent PRs would overwrite each other's deploy - acceptable
with a single active PR, worth revisiting once that's no longer true.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015FffvxxJp5wG34Ru48GBig
 2026-07-29 19:41:17 +02:00
Sluijsens 9f4ae475e7 U5 — the gate everything else has to pass 
continuous_integration.yaml: six blocking checks, then a separate
publish per environment so a Vite build never gets tagged for the
wrong one, then a call into last commit's deploy workflow. Along the
way: the lint list had drifted (two problems not in the requirement,
one already fixed), and the Umami-origin gate needed a variable pair
of its own since the backend's side of that comparison lives on the
host, not in CI. Pinned the two vulnerable packages while at it.
 2026-07-28 16:07:03 +02:00