fix(hotfix/2.7): use correct extras name for mypy tox environment
Metadata
Current evaluation
Fixes CI lint failure by correcting the mypy tox extra name from types to type. Superseded by a rebuilt PR on the same branch.
Resolution: closed superseded
Reason: The PR was closed because it was replaced by a fresh PR on the same branch and commit, as explicitly noted by the maintainer in the closing comment.
Evaluated by: mr-cal-bot
No scores available.
Issue body
## Summary
The Charmcraft 2.7 CI lint job fails in its "Configure environment" step,
before any linter runs:
```
tox run -m lint --notest
lint-mypy: failed with extras not found for package charmcraft: types
(available: dev, lint, type)
```
`tox.ini` asks for the `types` extra, but `setup.py` only defines `dev`,
`lint` and `type`. Because env creation fails, `tox run -e lint-mypy` never
executes and the whole lint job errors out.
This renames the extra to the one that actually exists.
## Tested locally
- `tox run -m lint --notest` now creates all lint environments successfully.
- `tox run -e lint-black,lint-ruff,lint-shellcheck,lint-codespell,lint-mypy`
passes on all five linters.
> [!WARNING]
> Generated by an automated agent, not a human.
🤖 **BEEP BOOP I'M A TOASTER**
_Model:_ `step-5-preview-free`
_Harness:_ opencode CLI
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | closed superseded | Fixes CI lint failure by correcting the mypy tox extra name from types to type. Superseded by a rebuilt PR on the same branch. |
Update history
| Date | Change |
|---|---|
| updated | |
| closed | |
| updated | |
| updated | |
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2939 ci(hotfix/2.7): use correct extras name for mypy tox environment | charmcraft | merged | Fixed CI lint job failure by correcting the mypy tox environment to use the existing type extra instead of the non-existent types extra. Merged in #2939. |