[Upd4ting]

Why

tooling-configs 0.6.0 adds the dependency:ranges check and removes the antelopejs-check-interface-ranges bin. An @antelopejs/* package ships breaking changes in minor releases, so a range left open past the next minor of its floor lets an install pull in a breaking release. This PR moves interface-api to tooling-configs 0.6.0 and caps every @antelopejs/* range on the newest minor published on npm, so the check passes and the module loads on the current core (ANT-2589, part of ANT-2512).

Ranges

Package	Field	Before	After	Newest on npm
@antelopejs/interface-core	peerDependencies	>=0.4.0 <1.0.0	>=0.5.1 <0.6.0	0.5.1
@antelopejs/interface-core	devDependencies	>=0.4.0 <1.0.0	>=0.5.1 <0.6.0	0.5.1
@antelopejs/core	devDependencies	^1.21.0	~1.23.0	1.23.0
@antelopejs/api	devDependencies	1.7.0	~1.7.3	1.7.3
@antelopejs/tooling-configs	devDependencies	^0.5.8	>=0.6.0 <0.7.0	0.6.0

Floors rise. The interface-core floor goes from 0.4.0 to 0.5.1, the line @antelopejs/core 1.22.0 and later require (>=0.5.1 <0.6.0). Core 1.21 was the last on 0.4.x. The lockfile now resolves api 1.7.3, core 1.23.0 and interface-core 0.5.1, one copy each, and the suites pass against them with no code change. The README compatibility table follows the new peer range.

No script called antelopejs-check-interface-ranges, so no script changes.

AGENTS.md now names @antelopejs/api 1.7.3, the version the suites run against, in place of 1.3.0.

Other changes from 0.6.0

antelopejs-sync in 0.6.0 adds .gitattributes (* text=auto eol=lf) and two rows to the managed rule table in AGENTS.md. sync:check fails without them.

Breaking

The @antelopejs/interface-core peer range no longer admits 0.4.x or anything from 0.6.0 on.

Proof

The dependency:ranges and sync:check steps of tooling-configs 0.6.0, every other step skipped with ANTELOPEJS_CHECKS_SKIP.

Before, on origin/main (d151fe5):

[sync:check]
Drift: .gitattributes; run antelopejs-sync
Drift: AGENTS.md; run antelopejs-sync
 ELIFECYCLE  Command failed with exit code 1.

[dependency:ranges]
package.json: devDependencies["@antelopejs/api"] is "1.7.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use "~1.7.0"
package.json: devDependencies["@antelopejs/core"] is "^1.21.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use "~1.21.0"
package.json: devDependencies["@antelopejs/interface-core"] is ">=0.4.0 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.4.0 <0.5.0"
package.json: peerDependencies["@antelopejs/interface-core"] is ">=0.4.0 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.4.0 <0.5.0"
Checks: 0 passed, 2 failed, 10 skipped.

After, on this branch:

Checks: 2 passed, 0 failed, 10 skipped.

pnpm test on this branch, against api 1.7.3, core 1.23.0 and interface-core 0.5.1:

  118 passing (448ms)

Every other step of pnpm run checks passed in the same run, and lockfile:singletons passes on the new lockfile.