Component
Dependency
Severity
P0 - Critical (crash/unusable)
Shiny Version
1.7.0
Python Version
3.12
Minimal Reproducible Example
Steps to reproduce
Inspect the dependency metadata of the two packages:
- shiny 1.7.0 (conda-forge): lists shinychat in run deps
- shinychat 0.6.1 (conda-forge): lists shiny in run deps
Behavior
Summary
shiny 1.7.0 added shinychat as a dependency. However, shinychat 0.6.1 lists shiny as a dependency, creating a circular dependency:
shiny → shinychat → shiny
Impact
This breaks any build system that enforces a strict dependency DAG (e.g. Bazel). The conda solver itself handles this fine, so it won't surface in typical conda install workflows — but it is visible in the conda package metadata and breaks downstream tooling that constructs a dependency graph.
Error Messages (if any)
Environment
Component
Dependency
Severity
P0 - Critical (crash/unusable)
Shiny Version
1.7.0
Python Version
3.12
Minimal Reproducible Example
Behavior
Summary
shiny 1.7.0 added shinychat as a dependency. However, shinychat 0.6.1 lists shiny as a dependency, creating a circular dependency:
shiny → shinychat → shiny
Impact
This breaks any build system that enforces a strict dependency DAG (e.g. Bazel). The conda solver itself handles this fine, so it won't surface in typical conda install workflows — but it is visible in the conda package metadata and breaks downstream tooling that constructs a dependency graph.
Error Messages (if any)
Environment