Repository navigation
build(deps): bump @antelopejs/tooling-configs to 0.5.0 - #36
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
A module generated from this template should start on the latest published
@antelopejs/tooling-configsand pass its own checks cleanly. 0.5.0 is the latest release on npm (latestdist-tag). Task ANT-1800, split from ANT-1694.What
@antelopejs/tooling-configsat^0.5.0and updatespnpm-lock.yaml.pnpm run syncwrites for 0.5.0: the newantelopejs/no-unsafe-object-assignrow inAGENTS.md,configandagentFilesinguardrails.suppressions.json, and the module-template text in.agents/skills/verify-template/SKILL.md.AGENTS.mdand the README checks row. Both named aguardrails.ratchet.jsonthat no module has, andantelopejs-checksskips the ratchet step without it. They now name the suppressions and lockfile checks thatpnpm run checksruns.tooling-configs#282 will fail
sync --checkon two things. This repo has neither of them, so neither needed a change:skipLibCheck(tsconfig.json,tsconfig.config.json,playground/tsconfig*.json). Onlybuildpasses--skipLibCheck, andtypecheck(tsc --noEmit) checks the sametsconfig.jsonprogram.releasescript and no.release-it.json.Proof
Before. On
mainwith only the version bumped to 0.5.0,pnpm run sync:checkexits 1:pnpm run checksexits 1:After. On this branch,
pnpm run sync:checkexits 0:pnpm run checksexits 0:pnpm build && pnpm --dir playground buildandpnpm exec antelopejs-check-interface-rangesboth exit 0.The verify layer ran every feature, because
package.jsonandpnpm-lock.yamlchanged (antelopejs-verify journey <run> --plan --jobs 4):The rerun after the docs commit (e4d5178) passed the same 10 journeys. An independent subagent judged the first run (7dc178a) PASS+NOTES.
formalfound no formal check covering the diff.doorsprintedOne-way-door: none flagged by path rules. Its note about the stale ratchet sentence is fixed by the docs commit.No verify failure is pre-existing on
main.