Testing project.optional-dependencies without duplicating dependencies

[topherbuckley]

I'm sure I'm misunderstanding something here, but I just want to have two hatch envs, call them release and debug as an example. I want users to be able to install a different list of dependencies for each (e.g. pip install example-package[debug] vs pip install example-package[release], and I want to use hatch to test that my package passes some basic tests using these exact same dependencies. For example:

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "example-package"
description = "An example Python package"
authors = [{ name = "Your Name", email = "[email protected]" }]
license = { file = "LICENSE" }

[project.optional-dependencies]
release = [
    "requests>=2.25,<3.0",  
    "numpy>=1.20,<2.0",     
]
debug = [
    "requests>=2.25,<3.0",
    "numpy>=1.20,<2.0",
    "pytest>=6.0,<7.0",     
]

[tool.hatch]
envs = { 
    release = { dependencies = ["requests>=2.25,<3.0", "numpy>=1.20,<2.0"] },
    debug = { dependencies = ["requests>=2.25,<3.0", "numpy>=1.20,<2.0", "pytest>=6.0,<7.0"] }
}

Do I really need to specify the dependencies and versions in two separate places like this? Am I fundamentally misunderstanding something here? I found a similar discussion here but no resolution.