
The critical that no gate blocked: 39 vulnerabilities and a green deploy
The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.
22 posts

The audit step claimed it blocked the build on known CVEs. It carried continue-on-error from day one. When pnpm audit found a CVSS 9.8 RCE in Astro, the deploy sailed through.

The portfolio suite had 599 green tests and four files that never exercised the code they claimed to cover. One called GET on a route that only exports POST. Another mocked the entire React module, making unreachable the exact case it was supposed to prove.

A visual regression test that depended on seeing the login error stopped being trustworthy because the preview server answered 502 on the very route the mock was supposed to intercept. The config now picks the server according to the test, and the Turnstile message stopped describing the system to say what the user must do.

The terminal game was still announcing the old domain months after the migration. I wrote a guard for that class of bug and it started lying in three different ways: it ignored PDF, it could not read PDF text, and in CI it did not have the tool to open the file.

The PR looked like a plain bump: the library went to 1.65, the binary stayed on 1.63, and the three CI shards died before running a single test.

A shell block on the last line of an already published post. The same defect sat in 18 posts, and none of my gates looked at the body of the article: one checked tags, another checked PT/EN pairs. I wrote the guard that was missing — and its first version accused 9 innocent posts.

Disk cleanup in the Dogwalk deploy lived in the middle of the workflow. On a self-hosted runner the work folder holds the checkout and the actions cache at the same time — and the 'harmless' step took down everything that came after it.

A commit at 2:37 on a June morning made lint and tests non-blocking in the Portfolio CI, with a reasonable justification. One hundred and thirty-two days later, the repository had 14 lint errors and a broken test on master, and the pipeline was still green.

A normalization rule at the edge layer was replacing the whole site's security policy with a two-line version, and only a test that hit real production noticed.

A file named test_portifolio.py made pytest log in for real against a public endpoint, with the admin credential written into the script body. Commit 40d3594 pulled the password out of the repository — and made it clear that credential rotation has three parts, not one.

How we fixed the database error, added Stripe Connect and automated Cloudflare Pages deployment.

How the team overcame CI loops, added Stripe Connect support, and automated Cloudflare Pages deployment.

The build job only fired on pushes to master and the deploy job only on tags; the two conditions never crossed, so no tag ever built or shipped. Behind that, the deploy still dialed SSH to a legacy host from a machine that was already the runner itself, and CI died on the very first language setup step.

The migration to native Linux took down all three daily posts: missing package manager, scripts full of Windows paths and lost state files. What it took to get the pipeline running again.

How Dogwalk evolved in October 2026: 1 379 tests, Stripe Connect and automatic deployment via Cloudflare Pages.

A blog with 366 pages needs to tell search engines it exists. The story of how the LifeLog gained JSON-LD, host verification, and IndexNow — and the retry the search engine's verification required.

A single config line with a placeholder where the key should be killed production login and signup for almost nine hours — and the real key existed nowhere at all. The story of the best-intentioned lockout I ever shipped, and of the doctor that diagnoses a pair without ever seeing the secret.

Nobody touched the code, yet Vercel kept rejecting the build: ERR_PNPM_EEXIST. The cause: a security cron ran pnpm audit fix with the Windows pnpm, regenerated a v10 lockfile while packageManager declared 9.12.3 — the saga of aligning local pnpm, packageManager and CI.

970 commits, 1456 tests, Stripe Connect, Open Design, and the saga of turning a pet marketplace into a platform that doesn't break on deploy.

July 2026 was the month my portfolio stopped getting new features and started fixing the ones it already had. A deep audit revealed 10 problems — from Pix to focus trap — and by the end, deployment was more automated than ever.

YAML indentation, missing dependencies, tests that need a running server — the classic pipeline debugging spiral.

How end-to-end tests transformed quality and confidence in Dogwalk's development — the real story of a stack that learned to test itself.