astro-cli
astro-cli copied to clipboard
Handle downgrades in "astro dev upgrade-test"
When running astro dev upgrade-test between Airflow 2.7.3 (astro-runtime:9.10.0) and Airflow 2.8.1, we get this in the dependency_compare.txt file:
Unknown Updates:
SQLAlchemy-JSONField 1.0.1.post0 >> 1.0.2
boto3 1.34.27 >> 1.33.13
botocore 1.34.27 >> 1.33.13
opentelemetry-semantic-conventions 0.41b0 >> 0.43b0
SQLAlchemy-JSONField and opentelemetry-semantic-conventions are not valid semver so I can understand we handle those as unknown. But it looks like we don't handle downgrades and just mark these as "unknown".
Can we make a separate grouping for downgraded dependencies? If possible, I'd follow the same grouping as for upgrades, so group by major, minor, patch downgrades.
Please paste terminal or playground output in a code block here
What CLI Version did you experience this bug? 1.21.0
This CLI bug is related to which Astronomer Platform?
- [ ] Astro
- [ ] Software
- [ ] None/Unknown
What Operating System is the above CLI installed on?
🪜 Steps To Reproduce
📸 Screenshots