Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependabot support for dependencies in hatch environments #775

Open
jorisroovers opened this issue Mar 9, 2023 · 1 comment
Open

Dependabot support for dependencies in hatch environments #775

jorisroovers opened this issue Mar 9, 2023 · 1 comment

Comments

@jorisroovers
Copy link

Something I’d like to have is dependabot support for dependencies in hatch environments, e.g. hatch.envs.test.dependencies.

Example dependencies section:

https://github.com/jorisroovers/gitlint/blob/7b0c255de3c3f51c62d8a182d7b1994450acf888/pyproject.toml#L83-L92

Related things I found:

  1. I’ve read Standard Python support dependabot/dependabot-core#3290, but AFAICT, that only pertains to top-level dependencies and optional-dependencies (which works well in my experience). I couldn’t find any existing issue for environment-level dependency support within the hatch or dependabot projects, although I’d be surprised if I’m the first one asking?

  2. I also had a quick glance at hatch-requirements-txt with the idea of splitting the test dependencies back out in a test-requirements.txt file so dependabot can pick them up. However, this feels like a step backwards and I think hatch-requirements-txt actually only supports project-level dependencies too (so this wouldn’t work).

  3. I also found the workaround by using the features option (although Bug: detached and skip-install envs silently ignore features option #729 would need to be fixed since I use skip-install=True), but I prefer not to expose the development dependencies to users, even as optional dependencies.

Is this something you think will eventually be supported, or is there another workaround available? Thanks!

@funkyfuture
Copy link
Contributor

isn't that an issue that concerns the dependabot developers?

also, what is the use-case? i'm assuming that hatch environments are used for development purposes and thus i don't see the need to prevent shipping possibly insecure software to the public. i'm also assuming that developers choose reasonable version specifications and keep their environments up-to-date, the latter is something that hatch does regularly for the developer.

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

No branches or pull requests

2 participants