Skip to content

Commit 23df7f1

Browse files
authored
Merge pull request #3509 from SUSE/for-deploy-16.1
🤖: Update build recipes for 16.1
2 parents 541551b + b260e2f commit 23df7f1

6 files changed

Lines changed: 24 additions & 14 deletions

File tree

cosign-image/Dockerfile

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@
1717

1818
#!BuildTag: suse/cosign:%%cosign_version%%-%RELEASE%
1919
#!BuildTag: suse/cosign:%%cosign_version%%
20-
#!BuildTag: suse/cosign:2.5
21-
#!BuildTag: suse/cosign:2
20+
#!BuildTag: suse/cosign:3.0
21+
#!BuildTag: suse/cosign:3
2222
#!BuildName: suse-cosign
23-
#!BuildVersion: 16.1.2.5
23+
#!BuildVersion: 16.1.3.0
2424
FROM bci/bci-micro:16.1 AS target
2525
FROM bci/bci-base:16.1 AS builder
2626
COPY --from=target / /target
@@ -31,7 +31,7 @@ RUN set -euo pipefail; \
3131
# sanity check that the version from the tag is equal to the version of cosign that we expect
3232
RUN set -euo pipefail; \
3333
[ "$(rpm --root /target -q --qf '%{version}' cosign | \
34-
cut -d '.' -f -2)" = "2.5" ]
34+
cut -d '.' -f -2)" = "3.0" ]
3535

3636
# cleanup logs and temporary files
3737
RUN set -euo pipefail; zypper -n --installroot /target clean -a; \

cosign-image/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ and a certificate issuer using the `--certificate-identity` and
2424
`--certificate-oidc-issuer` flags:
2525

2626
```ShellSession
27-
$ podman run registry.suse.com/suse/cosign:2.5 \
27+
$ podman run registry.suse.com/suse/cosign:3.0 \
2828
verify $IMAGE \
2929
--certificate-identity=$IDENTITY \
3030
--certificate-oidc-issuer=$OIDC_ISSUER
@@ -44,7 +44,7 @@ Valid payload is printed to stdout, in JSON format. Note that the
4444
signed payload includes the digest of the container image, which indicates that these "detached" signatures apply to the correct image.
4545

4646
```ShellSession
47-
$ podman run registry.suse.com/suse/cosign:2.5 verify --key cosign.pub $IMAGE_URI:1h
47+
$ podman run registry.suse.com/suse/cosign:3.0 verify --key cosign.pub $IMAGE_URI:1h
4848
The following checks were performed on these signatures:
4949
- The cosign claims were validated
5050
- The signatures were verified against the specified public key

cosign-image/cosign-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Tue Mar 3 08:51:22 UTC 2026 - SUSE Update Bot <bci-internal@suse.de>
3+
4+
- adjust for version update
5+
16
-------------------------------------------------------------------
27
Sun Jan 11 17:25:11 UTC 2026 - Dirk Müller <dmueller@suse.com>
38

helm-image/Dockerfile

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,10 @@
1717
#!ExclusiveArch: aarch64 ppc64le s390x x86_64
1818
#!BuildTag: suse/helm:%%helm_version%%-%RELEASE%
1919
#!BuildTag: suse/helm:%%helm_version%%
20-
#!BuildTag: suse/helm:3.19
21-
#!BuildTag: suse/helm:3
20+
#!BuildTag: suse/helm:4.1
21+
#!BuildTag: suse/helm:4
2222
#!BuildName: suse-helm
23-
#!BuildVersion: 16.1.3.19
23+
#!BuildVersion: 16.1.4.1
2424
FROM bci/bci-micro:16.1 AS target
2525
FROM bci/bci-base:16.1 AS builder
2626
COPY --from=target / /target
@@ -31,7 +31,7 @@ RUN set -euo pipefail; \
3131
# sanity check that the version from the tag is equal to the version of helm that we expect
3232
RUN set -euo pipefail; \
3333
[ "$(rpm --root /target -q --qf '%{version}' helm | \
34-
cut -d '.' -f -2)" = "3.19" ]
34+
cut -d '.' -f -2)" = "4.1" ]
3535

3636
# cleanup logs and temporary files
3737
RUN set -euo pipefail; zypper -n --installroot /target clean -a; \

helm-image/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@
1515
To run Helm, use the following command:
1616

1717
```ShellSession
18-
$ podman run --rm -it registry.suse.com/suse/helm:3.19 <helm-sub-command>
18+
$ podman run --rm -it registry.suse.com/suse/helm:4.1 <helm-sub-command>
1919
```
2020

2121
For instance, to display the Helm version, run:
2222
```ShellSession
23-
$ podman run --rm -it registry.suse.com/suse/helm:3.19 version --template='{{.Version}}'
24-
v3.19
23+
$ podman run --rm -it registry.suse.com/suse/helm:4.1 version --template='{{.Version}}'
24+
v4.1
2525
```
2626

2727
Refer to the full list of Helm commands, flags and environment variables, in the [official Helm documentation](https://helm.sh/docs/helm/helm/).
@@ -34,7 +34,7 @@ For a comprehensive guide on getting started with Helm, refer to the [official H
3434
To interact with a Kubernetes cluster, mount the Kubernetes configuration file (`kubeconfig`) from the container host into the container (use the `--net=host` flag to allow the container to use the host’s network):
3535

3636
```ShellSession
37-
$ podman run --rm -it --net=host -v /path/to/kubeconfig:/root/.kube/config:Z registry.suse.com/suse/helm:3.19
37+
$ podman run --rm -it --net=host -v /path/to/kubeconfig:/root/.kube/config:Z registry.suse.com/suse/helm:4.1
3838
```
3939

4040
## Licensing

helm-image/helm-image.changes

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
-------------------------------------------------------------------
2+
Tue Mar 3 08:51:22 UTC 2026 - SUSE Update Bot <bci-internal@suse.de>
3+
4+
- adjust for version update
5+
16
-------------------------------------------------------------------
27
Sun Jan 11 17:55:44 UTC 2026 - SUSE Update Bot <bci-internal@suse.de>
38

0 commit comments

Comments
 (0)