Repository navigation
build(deps): bump @antelopejs/tooling-configs to 0.5.1 - #107
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-api on
@antelopejs/tooling-configs0.5.1 so the repo passes the new guardrails cleanly, not just carries the version number (ANT-1858, parent ANT-1840).What changed
@antelopejs/tooling-configsdeclared^0.5.1, lockfile resolved to 0.5.1.pnpm run syncrefreshed two managed files.AGENTS.mdgains theantelopejs/no-read-then-insertrow (tooling-configs#287) and moves three sync rows from note-only tosync --check. The verify skill passes the judgement file toverdict --judgement.no-read-then-insertrule reports nothing here: this package reads and writes no table.no-inherited-key-lookupsuppression exists, so #291 has none to remove.anti-slop/no-unknown-parametersdirective (src/controller.ts,ParameterModifier'sprevious: unknown) still fires under 0.5.1 and stays. Narrowing that parameter would change the publishedParameterModifiertype, which is out of scope for a tooling bump. It is a type declaration, not a boundary that a schema.parsecan guard. It stays within its existing budget of 1. A ratchet entry would turn the rule off repo-wide, so this PR does not add one.src/is touched.Proof
Before:
mainwith 0.5.1 installed, beforesync.antelopejs-sync --check:pnpm run checks:After: this branch.
antelopejs-sync --check:pnpm run checks(typecheck, lint, format, knip, tests, size, suppressions, sync, verify layer):