Skip to content

build(deps): bump @antelopejs/tooling-configs to 0.5.0 - #83

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

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

Conversation

@Upd4ting

Copy link
Copy Markdown
Member

Why

Put interface-database on the latest published @antelopejs/tooling-configs (0.5.0) and make every check pass with it. Two warnings become sync --check failures in the next release (tooling-configs#282), so this PR clears them now. skipLibCheck was already absent from every tsconfig, so the remaining fix is that release now runs typecheck.

What changed

  • @antelopejs/tooling-configs goes from ^0.4.0 to ^0.5.0, lockfile updated. pnpm run sync refreshed .agents/setup, AGENTS.md, the verify skill and the README compat table.
  • release runs pnpm run typecheck after lint and before the build.
  • The new lockfile:singletons check found @antelopejs/interface-core resolved at 0.2.4 and 0.4.0. The lockfile now resolves 0.4.0 only. The specifier stays >=0.2.4 <1.0.0, as the check prescribes. The README compat table now says "Tested with 0.4.0".
  • antelopejs/no-unsafe-object-assign in src/tests/atomic_mutation.test.ts. The test still corrupts the terminal stage on purpose. It now does so through a structural { stage: string; options?: unknown; args: unknown[] } view, so the compiler checks the written fields. It needs no suppression or assertion.
  • anti-slop/no-runtime-typeof in scripts/test-staged-query.cjs. The instanceof Function checks on the root build become "run" in … and "atomicMutation" in …, which mirror the "run" in query is false checks on the staged half. The script later calls executableTable.atomicMutation(...).run(), which still exercises both methods.

No suppression was added. guardrails.suppressions.json is unchanged.

Proof

Before (origin/main with tooling-configs 0.5.0 installed)

pnpm run sync:check:


> @antelopejs/interface-database@0.3.1 sync:check /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> antelopejs-sync --check

Note: package.json: script "release" does not run "typecheck", so a release can publish a build that skipped the lib check. Add `pnpm run typecheck` to "release" before it builds or publishes, or to a release-it `before:init` hook.
Drift: .agents/setup; run antelopejs-sync
Drift: AGENTS.md; run antelopejs-sync
Drift: .agents/skills/verify-interface/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.
exit 1

pnpm run checks:


> @antelopejs/interface-database@0.3.1 checks /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> antelopejs-checks

[lint]

> @antelopejs/interface-database@0.3.1 lint /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> oxlint

src/tests/atomic_mutation.test.ts:277:42: error antelopejs(no-unsafe-object-assign): Object.assign writes a value over `stage` that the target's `stage` type does not accept, and TypeScript never compares the two: `Object.assign<T, U>` returns `T & U`. Assign the field directly so the compiler checks it.
src/tests/atomic_mutation.test.ts:277:42: error antelopejs(no-unsafe-object-assign): Object.assign writes a value over `args` that the target's `args` type does not accept, and TypeScript never compares the two: `Object.assign<T, U>` returns `T & U`. Assign the field directly so the compiler checks it.
scripts/test-staged-query.cjs:104:11: error anti-slop(no-runtime-typeof): `instanceof Function` is a `typeof` check in another form. Parse input at its I/O boundary, or move the check into a type guard such as `(value: unknown): value is Function`.
scripts/test-staged-query.cjs:105:11: error anti-slop(no-runtime-typeof): `instanceof Function` is a `typeof` check in another form. Parse input at its I/O boundary, or move the check into a type guard such as `(value: unknown): value is Function`.
scripts/test-staged-query.cjs:107:11: error anti-slop(no-runtime-typeof): `instanceof Function` is a `typeof` check in another form. Parse input at its I/O boundary, or move the check into a type guard such as `(value: unknown): value is Function`.
 ELIFECYCLE  Command failed with exit code 1.

[sync:check]

> @antelopejs/interface-database@0.3.1 sync:check /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> antelopejs-sync --check

Note: package.json: script "release" does not run "typecheck", so a release can publish a build that skipped the lib check. Add `pnpm run typecheck` to "release" before it builds or publishes, or to a release-it `before:init` hook.
Drift: .agents/setup; run antelopejs-sync
Drift: AGENTS.md; run antelopejs-sync
Drift: .agents/skills/verify-interface/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.

[lockfile:singletons]
pnpm-lock.yaml resolves "@antelopejs/interface-core" at 2 versions, and an interface package must load once:
  0.2.4, pulled by importer ".", @antelopejs/interface-database-catalog@0.0.3, @antelopejs/mongodb@1.6.0
  0.4.0, pulled by @antelopejs/core@1.21.0
  Set the direct specifier that locks the older copy to the newer version, run `pnpm install --lockfile-only`, then restore the specifier.
Checks: 7 passed, 3 failed.
 ELIFECYCLE  Command failed with exit code 1.
exit 1

After (this branch)

pnpm run sync:check:


> @antelopejs/interface-database@0.3.1 sync:check /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> antelopejs-sync --check

Guardrails are in sync.
exit 0

pnpm run checks:


> @antelopejs/interface-database@0.3.1 checks /home/debian/.t3/worktrees/interface-database/build-bump-tooling-configs
> antelopejs-checks

Checks: 10 passed, 0 failed.
exit 0

pnpm test:staged-query (not part of checks):

staged-query purity, AQL stages, and root compatibility: PASS

Verify layer

antelopejs-verify journey <run> --plan on this head ran every planned feature and exited 0. All 31 journeys passed, from smoke/through-core through types/usage-types.

Pre-existing, not a blocker

The pack's every-function and minor-bump journeys are not registered in this repo. features/smoke.md records that the declaration walker overflows the call stack on this package (tooling-configs#129, fixed by the unreleased tooling-configs#290), and smoke/through-core stands in for it. This is unchanged from origin/main.

@Upd4ting
Upd4ting merged commit dc052c9 into main Nov 10, 2026
7 checks passed
@Upd4ting
Upd4ting deleted the build/bump-tooling-configs branch November 10, 2026 15:38
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