fix(flask): don't enforce definition of base, build-base and platforms
Metadata
Current evaluation
Merged a Flask extension fix that stops enforcing mandatory base, build-base, and platforms definitions for gunicorn extensions. Approved by two reviewers and passed CI.
Suggested action: —
No scores available.
Issue body
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
Makes it an error for the any gunicorn based extension not to define a `base`, `build-base` and `platforms` key
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a Flask extension fix that stops enforcing mandatory base, build-base, and platforms definitions for gunicorn extensions. Approved by two reviewers and passed CI. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix that stops enforcing mandatory base, build-base, and platforms definitions for gunicorn-based extensions, resolving Flask deployment validation errors. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix that removes mandatory validation for base, build-base, and platforms keys in gunicorn-based Flask extensions, allowing these fields to be omitted. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1086 feat: default to bare base for flask, django and fastapi extensions | rockcraft | merged | Merged. Defaults to bare base for Flask, Django, and FastAPI extensions to reduce image size and attack surface. Approved by four reviewers and merged after CI checks passed. | |
| #839 fix: bare base gunicorn based extensions | rockcraft | merged | Merged fix for hardcoded Python 3.10 in gunicorn-based extensions, enabling version-specific configurations per base. Approved by three reviewers. A separate merge to the feature/pro-sources branch was requested for an upcoming demo. |