Apply `diff_level` from `azdev command-change meta-diff` into version calculation and breaking change detection

Open
#520 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli, release, tooling

Research direction

Start with the azdev command-change meta-diff entry point and the version calculation and breaking change detection paths; the issue does not name files or tests. Compare the current behavior with relevant changes in PR #8621, then establish whether diff_level should produce a warning or mark a breaking change and verify the resulting version behavior.

Written by the indexing model from the issue text.

Description

diff_level is introduced into azdev command-change meta-diff, but didn't apply into version calculation and breaking change detection. We need a proper way to warn developers about this change.

Relevant pr: https://github.com/Azure/azure-cli-extensions/pull/8621 choices lost, warning or breaking?

Dominant language
Python
Stars
91
Forks
134
Avg merge
2h 51m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-cli-dev-tools

All issues in Azure/azure-cli-dev-tools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.