[Upd4ting]

Why

interface-auth moves to tooling-configs 0.7.1, the newest release on npm, so pnpm run checks runs the dependency:ranges step that tooling-configs 0.6 introduced. That step requires every @antelopejs/* range to stop below the next minor, with ~ on a 1.x range. Each consumed package also moves to its newest minor on npm, so the next release loads beside the current stack, where core 1.23 already declares interface-core >=0.5.1. This is the interface-auth part of ANT-2512 (task ANT-2949).

What changes

• Every @antelopejs/* range sits on the newest minor on npm and stops below the next one. A 0.x range takes >=x.y.z <x.(y+1).0, and a 1.x range takes ~.
• The peer floors are the lowest patches the code works with: interface-api 0.3.0 and interface-core 0.5.0. The devDependencies pin the same ranges, and the lockfile resolves 0.3.3 and 0.5.1.
• The test config loads @antelopejs/api 1.7.4 instead of 1.3.0, because 1.3.0 depends on an interface-api older than 0.3. Its module lock in antelope-lock/ moves with it.
• antelopejs-sync refreshed the files the pack manages: the guardrails table in AGENTS.md, the README compatibility table, and a new .gitattributes.
• The Versioning section of AGENTS.md describes the capped ranges and names the dependency:ranges step.

No script called antelopejs-check-interface-ranges, so none had to be removed. No source file changed: the interface compiled and passed its tests against the new minors as it was.

The breaking part is the peer ranges. The interface now requires interface-api 0.3 and interface-core 0.5, so it no longer installs beside interface-api 0.0 to 0.2 or interface-core 0.2 to 0.4. No version number changes, and no release is cut.

Ranges

Package	Field	Before	After
@antelopejs/interface-api	peerDependencies	>=0.0.15 <1.0.0	>=0.3.0 <0.4.0
@antelopejs/interface-core	peerDependencies	>=0.2.4 <1.0.0	>=0.5.0 <0.6.0
@antelopejs/interface-api	devDependencies	^0.2.0	>=0.3.0 <0.4.0
@antelopejs/interface-core	devDependencies	^0.4.0	>=0.5.0 <0.6.0
@antelopejs/auth-jwt	devDependencies	1.0.3	~1.1.2
@antelopejs/core	devDependencies	^1.21.0	~1.23.3
@antelopejs/tooling-configs	devDependencies	^0.5.8	>=0.7.1 <0.8.0

The lockfile resolves interface-api 0.3.3, interface-core 0.5.1, auth-jwt 1.1.2, core 1.23.3 and tooling-configs 0.7.1.

Proof

dependency:ranges from tooling-configs 0.7.1, run on a detached checkout of origin/main (edca94c) and on this branch. Every other step was skipped for this run.

Before:

[dependency:ranges]
package.json: devDependencies["@antelopejs/auth-jwt"] is "1.0.3": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use "~1.0.3"
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: peerDependencies["@antelopejs/interface-api"] is ">=0.0.15 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.0.15 <0.1.0"
package.json: peerDependencies["@antelopejs/interface-core"] is ">=0.2.4 <1.0.0": AntelopeJS packages ship breaking changes in minor releases, so it must stop below the next minor; use ">=0.2.4 <0.3.0"
Checks: 0 passed, 1 failed, 12 skipped.

After:

Checks: 1 passed, 0 failed, 12 skipped.

pnpm run checks with only the test step skipped:

Checks: 12 passed, 0 failed, 1 skipped.

pnpm test on this branch, with api 1.7.4, interface-api 0.3.3 and interface-core 0.5.1:

  13 passing (19ms)

The floors were checked by installing interface-api 0.3.0 and interface-core 0.5.0 in place of the locked patches: pnpm run typecheck passed and pnpm test gave 13 passing. The lockfile was then restored.