Skip to content

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

Merged
Upd4ting merged 2 commits into
mainfrom
build/bump-tooling-configs
Nov 10, 2026
Merged

Upd4ting merged 2 commits into
mainfrom
build/bump-tooling-configs

Conversation

@Upd4ting

@Upd4ting Upd4ting commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

Why

A module generated from this template should start on the latest published @antelopejs/tooling-configs and pass its own checks cleanly. 0.5.0 is the latest release on npm (latest dist-tag). Task ANT-1800, split from ANT-1694.

What

  • Declares @antelopejs/tooling-configs at ^0.5.0 and updates pnpm-lock.yaml.
  • Commits what pnpm run sync writes for 0.5.0: the new antelopejs/no-unsafe-object-assign row in AGENTS.md, config and agentFiles in guardrails.suppressions.json, and the module-template text in .agents/skills/verify-template/SKILL.md.
  • No new lint finding came with the bump, so nothing is suppressed.
  • Fixes a stale sentence in AGENTS.md and the README checks row. Both named a guardrails.ratchet.json that no module has, and antelopejs-checks skips the ratchet step without it. They now name the suppressions and lockfile checks that pnpm run checks runs.

tooling-configs#282 will fail sync --check on two things. This repo has neither of them, so neither needed a change:

  • No tsconfig sets skipLibCheck (tsconfig.json, tsconfig.config.json, playground/tsconfig*.json). Only build passes --skipLibCheck, and typecheck (tsc --noEmit) checks the same tsconfig.json program.
  • The repo has no release script and no .release-it.json.

Proof

Before. On main with only the version bumped to 0.5.0, pnpm run sync:check exits 1:

> antelopejs-module@0.0.1 sync:check <repo>
> antelopejs-sync --check --profile template
Drift: AGENTS.md; run antelopejs-sync
Drift: guardrails.suppressions.json; run antelopejs-sync
Drift: .agents/skills/verify-template/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.

pnpm run checks exits 1:

> antelopejs-module@0.0.1 checks <repo>
> antelopejs-checks
[sync:check]
> antelopejs-module@0.0.1 sync:check <repo>
> antelopejs-sync --check --profile template
Drift: AGENTS.md; run antelopejs-sync
Drift: guardrails.suppressions.json; run antelopejs-sync
Drift: .agents/skills/verify-template/SKILL.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.
Checks: 10 passed, 1 failed.
 ELIFECYCLE  Command failed with exit code 1.

After. On this branch, pnpm run sync:check exits 0:

> antelopejs-module@0.0.1 sync:check <repo>
> antelopejs-sync --check --profile template
Guardrails are in sync.

pnpm run checks exits 0:

> antelopejs-module@0.0.1 checks <repo>
> antelopejs-checks
Checks: 11 passed, 0 failed.

pnpm build && pnpm --dir playground build and pnpm exec antelopejs-check-interface-ranges both exit 0.

The verify layer ran every feature, because package.json and pnpm-lock.yaml changed (antelopejs-verify journey <run> --plan --jobs 4):

PASS smoke/module-build (4.6 s)
PASS docs/scaffold-docs (3.4 s)
PASS git/scaffold-gitignore (4.6 s)
PASS module/scaffold-shape (0.3 s)
PASS module/module-build (reuses smoke/module-build, not run again)
PASS playground/playground-dev (11.2 s)
PASS tests/module-test (2.0 s)
PASS tests/module-test-fails (2.1 s)
PASS tooling/scaffold-lint-rejects (3.5 s)
PASS tooling/scaffold-checks (7.1 s)

The rerun after the docs commit (e4d5178) passed the same 10 journeys. An independent subagent judged the first run (7dc178a) PASS+NOTES. formal found no formal check covering the diff. doors printed One-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.

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