[PR PATCH] docker-buildx: update to 0.13.1.

[PR PATCH] docker-buildx: update to 0.13.1.

[TeddyDD]

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

There is a new pull request by TeddyDD against master on the void-packages repository

https://github.com/TeddyDD/void-packages-1 update-docker-buildx
https://github.com/void-linux/void-packages/pull/49403

docker-buildx: update to 0.13.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/49403.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-docker-buildx-49403.patch --]
[-- Type: text/x-diff, Size: 1111 bytes --]

From a6f97504a42d46acf2871de038c9c302b4f6a1be Mon Sep 17 00:00:00 2001
From: Daniel Lewan <daniel@teddydd.me>
Date: Wed, 20 Mar 2024 22:34:46 +0100
Subject: [PATCH] docker-buildx: update to 0.13.1.

---
 srcpkgs/docker-buildx/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/docker-buildx/template b/srcpkgs/docker-buildx/template
index 8cb2677f28583e..46b2a906ec31b0 100644
--- a/srcpkgs/docker-buildx/template
+++ b/srcpkgs/docker-buildx/template
@@ -1,6 +1,6 @@
 # Template file for 'docker-buildx'
 pkgname=docker-buildx
-version=0.12.1
+version=0.13.1
 revision=1
 build_style=go
 go_import_path="github.com/docker/buildx"
@@ -12,7 +12,7 @@ maintainer="Daniel Lewan <daniel@teddydd.me>"
 license="Apache-2.0"
 homepage="https://docs.docker.com/buildx/working-with-buildx/"
 distfiles="https://github.com/docker/buildx/archive/refs/tags/v${version}.tar.gz"
-checksum=9cc176ed55e7c423c23de35bd31df3b449261f1b90765c17f003bd4de86a6aa4
+checksum=6e77b77d9b7fae6f00955968569ec32673ae6e2bed31587ea016f9a5169b0f61
 
 post_install() {
 	vmkdir usr/libexec/docker/cli-plugins

Re: [PR PATCH] [Closed]: docker-buildx: update to 0.13.1.

[cinerea0]

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

There's a closed pull request on the void-packages repository

docker-buildx: update to 0.13.1.
https://github.com/void-linux/void-packages/pull/49403

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->

Re: docker-buildx: update to 0.13.1.

[cinerea0]

[-- Attachment #1: Type: text/plain, Size: 190 bytes --]

New comment by cinerea0 on void-packages repository

https://github.com/void-linux/void-packages/pull/49403#issuecomment-2016629452

Comment:
This appears to have been a duplicate? Closing.