Skip to content

fix(runtime): require discoverable core interfaces - #103

Closed
Upd4ting wants to merge 1 commit into
mainfrom
fix/require-interface-core-0.0.12
Closed

fix(runtime): require discoverable core interfaces#103
Upd4ting wants to merge 1 commit into
mainfrom
fix/require-interface-core-0.0.12

Conversation

@Upd4ting

@Upd4ting Upd4ting commented Aug 21, 2026

Copy link
Copy Markdown
Member

Summary

  • require @antelopejs/interface-core 0.0.12 so canonical root discovery includes module and runtime declarations
  • lock the Core runtime to the 0.0.12 candidate
  • exercise real Core module/runtime interface registration through canonical provider routing
  • update the packed consumer contract to require 0.0.12

Validation

  • pnpm lint
  • pnpm build
  • pnpm test:unit (672 passing)
  • targeted canonical provider-routing regression

Release ordering

This PR depends on AntelopeJS/interface-core#11 and can only install from the public registry after 0.0.12 is published.

Greptile Summary

Updates the Core runtime dependency to @antelopejs/interface-core 0.0.12 and adds coverage for canonical discovery and routing of Core module/runtime interfaces.

  • Updates the dependency manifest, lockfile, and packed-consumer contract to 0.0.12.
  • Exercises real Core interface registration and provider routing through the canonical package root.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or independently actionable non-blocking issue identified.

The dependency, lockfile, consumer contract, and canonical provider-routing coverage are updated consistently, and the investigation established no reachable incorrect behavior.

Important Files Changed

Filename Overview
package.json Raises the interface-core dependency requirement from 0.0.11 to 0.0.12.
pnpm-lock.yaml Resolves the root interface-core dependency to 0.0.12 with a matching snapshot.
test/integration/provider-routing.test.ts Adds integration coverage for discovering and routing the canonical Core module and runtime providers; no concrete defect was established.
test/package-consumer/run.ts Updates packed-manifest validation and the test consumer to require interface-core 0.0.12.

Reviews (1): Last reviewed commit: "fix(runtime): require discoverable core ..." | Re-trigger Greptile

Copy link
Copy Markdown
Member Author

@greptile review

Copy link
Copy Markdown
Member Author

Local candidate validation is complete against the byte-identical interface-core 0.0.12 tarball (b2eb98a0…): pnpm test passed all 672 unit tests, packed-consumer routing, and all three playground phases. The Core tarball was packed twice byte-identically (534393d8…, 155502 bytes), and an independent production-bootstrap matrix with real API/CMS/cms-api constructors returned HTTP 200 and clean lifecycle teardown. The Ubuntu check fails only because interface-core 0.0.12 is intentionally unpublished and npm returns 404 during install; release ordering remains interface-core 0.0.12 first, then Core.

Copy link
Copy Markdown
Member Author

Closed at Upd4ting's request: the Core 1.5 / multi-provider train is deferred and will be restarted manually later. This PR contains only work for that train; no independent fix is being retained. Do not merge or publish artifacts from this branch. Any future implementation should start from the then-current main branches and released package graph.

@Upd4ting Upd4ting closed this Aug 27, 2026
@Upd4ting
Upd4ting deleted the fix/require-interface-core-0.0.12 branch August 27, 2026 21:14
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