cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(email): record shared context evidence
CI and Deploy / test (pull_request) Successful in 4m23s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details

Browse Source
This commit is contained in:
cesnimda
2026-08-10 09:36:50 +02:00
parent ff547df175
commit 73ee095795
7 changed files with 43 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/verification/dep-001-frontend-advisories.md
+4 -2
View File
@@ -2,7 +2,7 @@
Updated: 2026-08-10
Status: `VERIFIED LOCALLY`. Remote run 608 confirms the dependency-audit step passes; the pull-request job then failed on an unrelated stale Career Workspace smoke assertion. Live deployment still requires merge-to-main and production verification.
Status: `VERIFIED LOCALLY`. Remote pull-request run 609 passes the complete CI job, including dependency audit and browser smoke. Live deployment still requires an approved merge-to-main and production verification.
## Trigger
@@ -26,10 +26,12 @@ The live deployment pipeline failed its frontend dependency audit on five adviso
- Commit: `b55a592` (pushed to `release-readiness`).
- Gitea pull-request run 608: `Audit frontend dependencies` PASS; the job advanced through frontend tests and failed later at `Test browser smoke flows` because `e2e/smoke.spec.ts` still expected intentionally removed page copy.
- Corrected smoke assertion: full local Playwright suite 4/4 passed against disposable local API/frontend data.
- Smoke correction commit: `75bf144` (pushed to `release-readiness`).
- Gitea replacement run 609: complete pull-request test job PASS in 4m20s. The deploy job was skipped by its intentional `push`/`main` condition.
## Remaining gate
Confirm a new pull-request run passes end to end, then merge/deploy from `main` and run production route smoke. No production access or deployment was performed in this session.
Merge only when the full release-readiness branch is approved, then observe the `main` deploy and run production route smoke. No production access or deployment was performed in this session.
## Rollback