Repository navigation
build(deps): bump @antelopejs/tooling-configs to 0.5.0 - #83
Merged
Merged
Conversation
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
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.
Why
Put interface-database on the latest published
@antelopejs/tooling-configs(0.5.0) and make every check pass with it. Two warnings becomesync --checkfailures in the next release (tooling-configs#282), so this PR clears them now.skipLibCheckwas already absent from every tsconfig, so the remaining fix is thatreleasenow runstypecheck.What changed
@antelopejs/tooling-configsgoes from^0.4.0to^0.5.0, lockfile updated.pnpm run syncrefreshed.agents/setup,AGENTS.md, the verify skill and the README compat table.releaserunspnpm run typecheckafter lint and before the build.lockfile:singletonscheck found@antelopejs/interface-coreresolved 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 with0.4.0".antelopejs/no-unsafe-object-assigninsrc/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-typeofinscripts/test-staged-query.cjs. Theinstanceof Functionchecks on the root build become"run" in …and"atomicMutation" in …, which mirror the"run" in queryis false checks on the staged half. The script later callsexecutableTable.atomicMutation(...).run(), which still exercises both methods.No suppression was added.
guardrails.suppressions.jsonis unchanged.Proof
Before (origin/main with tooling-configs 0.5.0 installed)
pnpm run sync:check:pnpm run checks:After (this branch)
pnpm run sync:check:pnpm run checks:pnpm test:staged-query(not part ofchecks):Verify layer
antelopejs-verify journey <run> --planon this head ran every planned feature and exited 0. All 31 journeys passed, fromsmoke/through-corethroughtypes/usage-types.Pre-existing, not a blocker
The pack's
every-functionandminor-bumpjourneys are not registered in this repo.features/smoke.mdrecords that the declaration walker overflows the call stack on this package (tooling-configs#129, fixed by the unreleased tooling-configs#290), andsmoke/through-corestands in for it. This is unchanged from origin/main.