`expiration` in `deprecate_info` frequently breaks release pipeline
Open
act-platform-engineering-squad
Azure CLI Team
CI
common issue
feature-request
Release
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 60
Description
When releasing Azure CLI, version bump PRs (such as https://github.com/Azure/azure-cli/pull/27790) are frequently broken by `expiration` in `deprecate_info`. Urgent fixes are required to unblock the release pipeline.
- https://github.com/Azure/azure-cli/pull/18133
- https://github.com/Azure/azure-cli/pull/21892
- https://github.com/Azure/azure-cli/pull/25344
- https://github.com/Azure/azure-cli/pull/25664
- https://github.com/Azure/azure-cli/pull/26477
- https://github.com/Azure/azure-cli/pull/27791
**Possible solutions**
1. Avoid using `expiration` in `deprecate_info`, so that version bump PR won't be affected by it.
2. Introduce detection in CI before version bump.
Contributor guide
Assessment
This issue has not been assessed yet.