ci: restrict pypi job to amd64
Metadata
Current evaluation
Merged. The pull request restricts the PyPI publishing job to amd64 architecture, as the underlying docker image is always amd64. Approved by two reviewers with passing CI checks.
Suggested action: —
No scores available.
Issue body
The `gh-action-pypi-publish` pulls in a docker image to do the actual publishing, and said image is apparently always amd64
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged. The pull request restricts the PyPI publishing job to amd64 architecture, as the underlying docker image is always amd64. Approved by two reviewers with passing CI checks. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to restrict the CI pypi job to amd64 architecture, ensuring compatibility with the amd64-only docker image used by the publishing action. Integrated by maintainer tigarmo. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #249 ci: run pypi publish job on a specific amd64, noble runner | craft-platforms | merged | Merged a CI update to run the PyPI publish job on an amd64 Ubuntu Noble runner, resolving architecture compatibility. Approved by two reviewers with all checks passing. | |
| #604 ci: build and publish artifacts on amd64 | craft-application | merged | Merged a CI update to build and publish artifacts on amd64. This resolves a platform mismatch warning with the PyPI publish action and aligns with available build infrastructure. Approved by reviewers and merged. |