Skip to content

Adding dependencies to a dev package doesn't quite work. #4644

@orenbenkiki

Description

@orenbenkiki
  1. dev a package in the global environment
  2. Add a new dependency to that package's Project.toml
  3. The global manifest's dep list for the dev'd package goes stale
  4. Any LOAD_PATH stacking that hits @v#.# first sees the stale deps

Isn't the whole point of dev packages that they are, well, being developed? I had expected any other environment that loads the dev package to see that the package has changed and reload its new dependencies list.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions