Skip to content

build(deps): bump @antelopejs/tooling-configs to 0.5.1 - #109

Merged
Upd4ting merged 1 commit into
mainfrom
build/tooling-configs-0.5.1
Nov 10, 2026
Merged

Upd4ting merged 1 commit into
mainfrom
build/tooling-configs-0.5.1

Conversation

@Upd4ting

Copy link
Copy Markdown
Member

Why

Put this repository on @antelopejs/tooling-configs 0.5.1 and adopt its antelopejs/no-read-then-insert check (tooling-configs#287), which catches a read that decides an insert another replica can race. 0.5.1 also relaxes antelopejs/no-inherited-key-lookup (tooling-configs#291) and narrows anti-slop/no-unknown-parameters to trust only schema-library decoders (tooling-configs#281). Part of ANT-1663. This is this repository's 0.5.1 bump for ANT-1840.

What changes

  • @antelopejs/tooling-configs goes from ^0.5.0 to ^0.5.1, and the lockfile resolves 0.5.1.
  • pnpm run sync updated the managed AGENTS.md block, which adds the no-read-then-insert row and moves three skipLibCheck/typecheck rows to antelopejs-sync --check. It also updated .agents/skills/verify-interface/SKILL.md, where verdict now takes --judgement <file>.
  • The new rule is error in the preset that oxlint.config.ts extends, so the lint step of CI runs it with no config change. The preset turns it off for test files.

No source file changes.

Findings from main with 0.5.1

pnpm exec oxlint --report-unused-disable-directives on main with 0.5.1 reports no diagnostics:

{ "diagnostics": [], "number_of_files": 65, "number_of_rules": 164 }
  • antelopejs/no-read-then-insert has no findings. This package declares tables and models and runs no startup read that decides an insert.
  • anti-slop/no-unknown-parameters has no new findings. Its 8 existing directives still suppress live diagnostics, so none is unused.
  • The no-inherited-key-lookup relaxation frees no directive, because the repository has none for that rule.

No fix was needed, so there is no before and after test. guardrails.suppressions.json is unchanged, and no guardrails.ratchet.json was needed.

Note on ANT-1709 (not fixed here)

HashModifier.lock in src/modifiers/hash.ts calls scryptSync on every write of a hashed field. ANT-1709 measured about 135 ms of event-loop block per password write. I think this deserves its own task. The fix is not local, because lock runs inside the synchronous setter and the insert/update conversions. Moving the hash to the thread pool needs an async lock path through the modifier chain, which changes the exported modifier contract. That is a minor bump of this interface, and it needs a matching change in the implementing modules. testAsync already exists for the read side, so only the write path remains.

Proof

pnpm run checks (typecheck, lint, format, knip, tests, size, suppressions, sync check, verify types and lockfiles):

Checks: 11 passed, 0 failed.

Exported surface unchanged:

API: 1 packages, 25 entries unchanged against origin/main (committed HEAD).
API: skipped .agents/skills/verify-interface, private.
Runtime API: 1 packages, 13 entries unchanged against origin/main (committed HEAD).
No behavioural probe ran.

Suppressions in authored code files (origin/main and committed HEAD). A lint directive counts once per rule it names; * is a directive naming none.

Suppressions base HEAD
Lint suppressions, all rules 28 28
Lint suppressions, anti-slop/no-unknown-parameters 8 8
Lint suppressions, anti-slop/no-unknown-returns 1 1
Lint suppressions, anti-slop/no-unsafe-dictionary-type 10 10
Lint suppressions, typescript/no-unnecessary-type-parameters 4 4
Lint suppressions, typescript/no-unsafe-assignment 2 2
Lint suppressions, typescript/no-unsafe-return 3 3
@ts-expect-error 0 0
@ts-ignore 0 0
SAFETY: comments 8 8
Lint config rule-offs, all rules 0 0

@Upd4ting
Upd4ting merged commit d040fd3 into main Nov 10, 2026
8 checks passed
@Upd4ting
Upd4ting deleted the build/tooling-configs-0.5.1 branch November 10, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant