-
Notifications
You must be signed in to change notification settings - Fork 1
drop the hono age-gate exclude once its release matures #837
Copy link
Copy link
Open
Labels
area/platformarea: deploy, db hosting, monorepo, CIarea: deploy, db hosting, monorepo, CIupkeepevent- or date-triggered maintenance; body carries a trigger line the weekly sweep evaluatesevent- or date-triggered maintenance; body carries a trigger line the weekly sweep evaluatesupkeep-readyupkeep trigger has fired; cleanup is actionable nowupkeep trigger has fired; cleanup is actionable now
Description
Metadata
Metadata
Assignees
Labels
area/platformarea: deploy, db hosting, monorepo, CIarea: deploy, db hosting, monorepo, CIupkeepevent- or date-triggered maintenance; body carries a trigger line the weekly sweep evaluatesevent- or date-triggered maintenance; body carries a trigger line the weekly sweep evaluatesupkeep-readyupkeep trigger has fired; cleanup is actionable nowupkeep trigger has fired; cleanup is actionable now
bunfig.tomlexcludeshonofrom the 7-dayminimumReleaseAgegate so the tree could adopt theadvisory-patched release (hono 4.13.0, patching GHSA-8j4g-w8fx-2239 — the CORS-middleware ReDoS) the
day it shipped. Published 2026-08-03, it ages past the gate ~2026-08-10.
When the trigger fires:
honoentry and its comment line fromminimumReleaseAgeExcludesinbunfig.tomlbun installand confirmbun run auditstill passes