mainWhat we shipped.
One line per merged pull request, dated by merge day. Generated by the same automation that pushes the code, so the only delay between "we shipped it" and "it appears here" is a CI run.
What changed most recently in VectraSEO?
The changelog lists the latest merged pull requests by release date, with the newest shipped change first and older releases kept in the project archive.
Last updated·
- PR_2041CHANGEDfix(ga4): retry transient report failures and keep AI referrals
Nightlamp opened two unresolved production warnings for VectraSEO:
- PR_2039CHANGEDdocs(monitoring): record the tightened heartbeat and the router test
Follow-up to the 2026-11-11 monitor incident.
- PR_2037CHANGEDfix(publish): seed claim repair from the rejected sentence alone
Prod
post_47b1c7ef5eda4a7d(Emcognito, 2026-11-11) was rejected by the destination with422 capability_claim_violationforyour own domain, in the sentence:
- PR_2035CHANGEDperf(lambda): right-size PipelineWorker to 768 MB
PipelineWorkeris 24% of this account's Lambda GB-second usage (84,831 GB-s in 10 days) and the second-largest consumer after Nightlamp's probe runner. It runs at 1024 MB.
- PR_2033CHANGEDfix(canary): re-freeze post_metadata guardrail from instrumented days
The live
post_metadatacanary baseline is frozen from 2026-08-25 → 2026-09-24.metadata_ai_repair_passed— the field behindmetadata_repair_pass_rate— shipped on **20...
- PR_2031CHANGEDfix(canary): report deepseek_route_reverted from current canary state
The Nightlamp pipeline heartbeat stayed down on
deepseek_route_reverted=1.0after thepost_metadatarevert had been cleared in prod (its canary row is back torunning). - PR_2029CHANGEDfix(canary): report loss_rate only from 20 outcomes
Raises the heartbeat's loss_rate minimum sample from 10 to 20 (
_LOSS_RATE_MIN_SAMPLE). - PR_2027CHANGEDfix(canary): judge post_metadata on the posts that reached the repair call
On 2026-11-06 at 03:15 UTC the canary reverted
post_metadatato Gemini:metadata_first_pass_ratewas 50/53 against a 0.9894 baseline (p=0.0188).
- PR_2025CHANGEDchore(alarms): retire the seven pipeline CloudWatch alarms
Remove the seven redundant pipeline alarms from
WorkerStack:
- PR_2023CHANGEDfix(broken_images): stop flagging url() inside CSS data URIs and commas in srcset; log scan summary (#2017)
Two production monitors were reporting broken images that aren't broken, so I fixed that and two other defects that turned up during QA.
- PR_2020CHANGEDchore(deps): bump follow-redirects from 1.16.1 to 1.16.2 in /frontend
Bumps follow-redirects from 1.16.1 to 1.16.2.
- PR_2019CHANGEDfix(infra): prune old Lambda SnapStart versions after deploy
Add
infrastructure/scripts/prune_lambda_versions.py, a tested, dry-run-by-default pruner that keeps every aliased Lambda version (including weighted-routing targets) plus one... - PR_2015CHANGEDfeat(monitoring): detect broken images in site health scans
Adds a
broken_imagessite-health rule that requests the image references on every scanned page and reports confirmed failures instead of letting a broken image pass a markup-o...
- PR_2013CHANGEDfeat(monitoring): carry pipeline alarm inputs on the Nightlamp heartbeat
The seven VectraSEO pipeline CloudWatch alarms can move to Nightlamp's existing heartbeat payload thresholds, but only if the heartbeat carries their inputs. Today it sends just...