11 Commits

Author	SHA1	Message	Date
Sviatoslav Sydorenko	e0449d218c	🧪 Integrate a unified alls-green GHA status	2025-01-24 03:30:02 +01:00
Brendon Smith	f81cd95ad9	Tag Docker images with Git SHA ... PR https://github.com/pypa/gh-action-pypi-publish/pull/230 updated the action to pull Docker images from GHCR instead of building Docker images each time the workflow runs. As part of this PR, a new GitHub Actions workflow was added that builds Docker images and pushes them to GitHub Container Registry (GHCR). Actions can be referenced in various ways. The Docker build workflow covers most of the action references, but does not push Docker images tagged with the Git commit ID (Git SHA). This commit will add Docker tags for referencing the action with a Git SHA. GitHub Actions only supports references by the full 40 character SHA. If users try to reference the action by a short SHA like `1234567`, they will get an error like, "Unable to resolve action `pypa/gh-action-pypi-publish@1234567`, the provided ref `1234567` is the shortened version of a commit SHA, which is not supported. Please use the full commit SHA `1234567890123456789012345678901234567890` instead." https://github.com/pypa/gh-action-pypi-publish/pull/230 https://github.com/pypa/gh-action-pypi-publish/issues/290 https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/using-pre-written-building-blocks-in-your-workflow#using-shas	2024-11-11 18:58:36 -05:00
Brendon Smith	36965cb24a	Run smoke tests before Docker builds ... https://github.com/pypa/gh-action-pypi-publish/pull/230#discussion_r1787027821	2024-11-04 16:35:15 -05:00
Brendon Smith	da554410b0	Move smoke test to reusable workflow	2024-11-04 16:35:14 -05:00
Brendon Smith	80b1d50e0d	Make workflow_dispatch Docker tag input required ... https://github.com/pypa/gh-action-pypi-publish/pull/230#discussion_r1759496153	2024-11-04 16:35:14 -05:00
Brendon Smith	cfb9d93a26	Add Docker tags for major and minor versions	2024-11-04 16:35:14 -05:00
Brendon Smith	5ded5310e7	Add workflow_dispatch trigger for Docker builds	2024-11-04 16:35:13 -05:00
Brendon Smith	cf5ce177da	Use YAML block strip syntax (>-) where possible	2024-11-04 16:35:13 -05:00
Brendon Smith	0d8d5059c8	Separate docker login and docker push ... https://github.com/pypa/gh-action-pypi-publish/pull/230#discussion_r1578694138	2024-11-04 16:35:13 -05:00
Brendon Smith	e453f8c630	Fix pre-commit errors	2024-11-04 16:35:13 -05:00
Brendon Smith	783267be69	Build Docker image and push to GHCR ... Up to this point, the project has been set up as a Docker action referencing the Dockerfile. The downside to using the Dockerfile for the action is that the Docker image must be built every time the action is used. This commit will set up the project to build the Docker image and push it to GitHub Container Registry (GHCR). This change will speed up user workflows every time the action is used because the workflows will simply pull the Docker image from GHCR instead of building again. Changes: - Add required metadata to Dockerfile - Build container image with GitHub Actions - Push container image to GHCR Docker actions support pulling in pre-built Docker images. The downside is that there's no way to specify the correct Docker tag because the GitHub Actions `image` and `uses:` keys don't accept any context. For example, if a user's workflow has `uses: pypa/gh-action-pypi-publish@release/v1.8`, then the action should pull in a Docker image built from the `release/v1.8` branch, something like `ghcr.io/pypa/gh-action-pypi-publish:release-v1.8` (Docker tags can't have `/`). The workaround is to switch the top-level `action.yml` to a composite action that then calls the Docker action, substituting the correct image name and tag.	2024-11-04 16:35:13 -05:00