GitHub Dependency Graph not detecting PyPI packages in monorepo #5297
Unanswered
kugesan1105
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We maintain jaseci-labs/jaseci, a monorepo that publishes 7 packages to PyPI:
jaclang(core language)jac-byllm,jac-client,jac-scale,jac-super,jac-mcp(plugins)jaseci(meta-package)The problem
When we check the Dependency Graph → Dependents tab, GitHub only recognizes 2 of our 7 packages (
jaseciandjac-client). The other 5 packages, includingjaclangwhich is our most-used package, do not appear in the package dropdown at all.The 33 repositories shown under
jaseciare from an older era when this was a single-package repo. We transitioned to a multi-package monorepo structure, and since then GitHub hasn't properly detected the new packages.What we've verified
All our packages have correct
[project.urls]metadata in theirpyproject.tomlfiles pointing back to the repository:We also create release tags for each package (e.g.,
jaclang-v2.3.5) through our automated release workflow.Despite this, GitHub's dependency graph does not recognize most of our packages.
Our latest release (https://github.com/jaseci-labs/jaseci/releases/tag/v2.3.7) shows all 7 packages being published together with proper artifacts and tags.
Request
Is there a specific configuration, metadata format, or process we should follow to get GitHub to properly detect all packages published from a monorepo? Do we need to file an issue with GitHub, or is this a known limitation that requires manual intervention from their side? What would be the best next step here?
Beta Was this translation helpful? Give feedback.
All reactions