Problem
The CLI currently has no automated release schedule, which means merged features can sit on main for an extended and unpredictable period before they are available to users.
A concrete example is #605. This PR was merged on March 31, 2026, bringing the CLI into alignment with the update-types support that landed in dependabot-core. As of today it is still not available in a released CLI version which hinders to availability to test and troubleshoot that feature from the cli.
Proposed solutions
- Adopt a scheduled, automated release workflow like what
dependabot-core already does: a weekly release cut automatically via GitHub Actions, without requiring any manual intervention.
or
- Create a release on every merge using tools like Semantic Release and similar
Problem
The CLI currently has no automated release schedule, which means merged features can sit on
mainfor an extended and unpredictable period before they are available to users.A concrete example is #605. This PR was merged on March 31, 2026, bringing the CLI into alignment with the
update-typessupport that landed independabot-core. As of today it is still not available in a released CLI version which hinders to availability to test and troubleshoot that feature from the cli.Proposed solutions
dependabot-corealready does: a weekly release cut automatically via GitHub Actions, without requiring any manual intervention.or