chore(ci): bump housekeeping action to v0.21.0 - #90
Draft
zmaril wants to merge 3 commits into
Draft
Conversation
Picks up the checks and verdict changes released in v0.20.0.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
straitjacket | 03003e5 | Commit Preview URL Branch Preview URL |
Jul 18 2026, 09:40 PM |
GitHub's allow_auto_merge is on for this repo, so declare it here to match. This key is only understood by housekeeping v0.20.0, which is why it ships in the same PR as the version bump: on v0.19.0 the config check rejects it as an unknown key.
v0.21.0 supersedes v0.20.0: it adds the strict-status-checks check and fixes three v0.20.0 defects, two of which made that release's own fixes unsafe to run.
zmaril
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pinned
zmaril/housekeepingaction to v0.21.0 (release notes).Originally opened against v0.20.0 and repointed — v0.21.0 supersedes it. (The branch name still says
v0.20.0; renaming it would mean a new PR, so it's left alone.)Why not v0.20.0
Rolling v0.20.0 across the fleet surfaced three defects, two of which made its own
housekeeper fixunsafe to run:fix ci-existsoverwrote existing CI. It wrote.github/workflows/ci.ymlwith no existence guard, so on a repo whose CI merely lacked one language's test step it replaced the entire hand-written workflow with a generic stub.lockfilesdemanded a lockfile that cannot exist. A dependency-free package has none to produce — bun deletes an empty one outright — so the only way to pass was to fabricate a foreign lockfile.repo-metaparsed its own documentation. A README documenting the marker syntax had its fenced example read as the declaration, sofix repo-metawould push a placeholder over the repo's real description and topics.All three are fixed in v0.21.0, along with a new
[lockfiles] ignoreescape hatch for packages that keep lockfiles untracked on purpose.What this changes here
v0.21.0 also adds
strict-status-checks(required): the default branch must require branches be up to date before merging. That setting has already been enabled on this repo's ruleset, along withallow_update_branch, so this check passes.v0.20.0's stricter nested-aware detection still applies —
lockfiles,dependabot,ci-exists,coverageandgitignorenow grade nested packages per-directory. Any remaining failure on this PR is a genuine gap, not a tooling bug.Draft on purpose:
housekeepingis a required status check here, so confirm the run is green before merging.