generated from actions/container-action
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add linux arm64 images to the build process #405
Merged
johnboyes
merged 2 commits into
agilepathway:master
from
ivan-leschinsky:add-linux-arm-images
Oct 21, 2023
Merged
Add linux arm64 images to the build process #405
johnboyes
merged 2 commits into
agilepathway:master
from
ivan-leschinsky:add-linux-arm-images
Oct 21, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ivan-leschinsky
force-pushed
the
add-linux-arm-images
branch
from
October 11, 2023 10:24
4afe028
to
aa17089
Compare
Hi @ivan-leschinsky, thanks for the contribution - I'll review it in the next couple of days, hopefully Sunday 👍🏻 |
johnboyes
added
the
minor
Semantic versioning: new functionality that is backwards compatible
label
Oct 21, 2023
johnboyes
approved these changes
Oct 21, 2023
Released in v1.6.0 - thanks again @ivan-leschinsky for the contribution 🙏🏻 |
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
A recent change, #405, which added ARM64 Docker images to the build process, introduced a bug whereby the new Docker images for each release are no longer being tagged `latest`, as they should be. This commit adds a test to catch this bug, and we will fix the bug in a subsequent commit.
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
A recent change, #405, which added ARM64 Docker images to the build process, introduced a bug whereby the new Docker images for each release are no longer being tagged `latest`, as they should be. This commit adds a test to catch this bug, and we will fix the bug in a subsequent commit.
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
A recent change, #405, which added ARM64 Docker images to the build process, introduced a bug (see #419) whereby the new Docker images for each release are no longer being tagged `latest`, as they should be. This commit adds a test to catch this bug, and we will then fix the bug in a subsequent commit.
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
A recent change, #405, which added ARM64 Docker images to the build process, introduced a bug (see #419) whereby the new Docker images for each release are no longer being tagged `latest`, as they should be. This commit adds a test to catch this bug, and we will then fix the bug in a subsequent commit.
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
A recent change, #405, which added ARM64 Docker images to the build process, introduced a bug (see #419) whereby the new Docker images for each release are no longer being tagged `latest`, as they should be. This commit adds a test to catch this bug, and we will then fix the bug in a subsequent commit.
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
The bug was inadvertently introduced by #405, when we migrated to a later version of the [Docker `build-push-action`][1]. [1]: https://github.com/docker/build-push-action Fixes #419
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
The bug was inadvertently introduced by #405, when we migrated to a later version of the [Docker `build-push-action`][1]. [1]: https://github.com/docker/build-push-action Fixes #419
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
The bug was inadvertently introduced by #405, when we migrated to a later version of the [Docker `build-push-action`][1]. [1]: https://github.com/docker/build-push-action Fixes #419
johnboyes
added a commit
that referenced
this pull request
Jan 19, 2024
The bug was inadvertently introduced by #405, when we migrated to a later version of the [Docker `build-push-action`][1]. [1]: https://github.com/docker/build-push-action Fixes #419
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Released and checked in my repo
https://hub.docker.com/repository/docker/vanopiano/pull-request-label-checker/tags?page=1&ordering=last_updated