Skip to content

feat: capability-based dependency checking at runtime#63

Open
BimaPangestu28 wants to merge 1 commit into
mainfrom
feat/capability-based-dependency-check
Open

feat: capability-based dependency checking at runtime#63
BimaPangestu28 wants to merge 1 commit into
mainfrom
feat/capability-based-dependency-check

Conversation

@BimaPangestu28
Copy link
Copy Markdown
Member

Summary

  • Upgrade dependency_resolver::check_all to fall back to capability-based matching when pack_id not found directly
  • Build capability index from all pack manifests in the bundle
  • Improved warning messages suggest which capabilities to add
  • Log capability-satisfied dependencies for visibility
  • Also: fix public URL display to show route paths alongside ngrok/cloudflared URLs

Test plan

  • cargo test passes
  • cargo check clean
  • Start bundle with state-memory providing greentic:state/state-store and verify capability match logged
  • Start bundle without state pack and verify improved warning message

The runtime dependency checker now falls back to capability-based
matching when a dependency pack_id is not found directly. Builds a
capability index from all pack manifests and checks if
required_capabilities are satisfied by any pack. Improved warning
messages suggest which capabilities to add.

Also: fix public URL display to include route paths, improve startup
info messages for capability-satisfied dependencies.

Bump version to 0.4.40.
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