shipwright-io / triggers

Event-driven Shipwright Builds
Apache License 2.0
6 stars 7 forks source link

Bump github.com/shipwright-io/build from 0.11.1-0.20230807070125-1156efa24b0a to 0.12.0 #69

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/shipwright-io/build from 0.11.1-0.20230807070125-1156efa24b0a to 0.12.0.

Release notes

Sourced from github.com/shipwright-io/build's releases.

Shipwright Build release v0.12.0

Release changes since v0.11.0

Features

#1398 by @​apoorvajagtap: The Strategy struct does not have an APIVersion field anymore.

#1384 by @​SaschaSchwarze0: Installing a nightly release now requires you to run a post-script that sets up the TLS certificate of the conversion webhook

#1370 by @​apoorvajagtap: The BuildAh sample build strategies now do not anymore run privileged containers

#1342 by @​SaschaSchwarze0: The shipwright-build namespace is now configured to enforce restricted PodSecurity. The shipwright-build-controller deployment was updated to fulfill all requirements.

#1323 by @​SaschaSchwarze0: Buildpacks sample build strategies are updated to the latest Heroku version and a newer platform API version

#1302 by @​qu1queee: Introduce conversion-webhook to convert SHP Custom Resources from v1beta1 to v1alpha1.

#1268 by @​SaschaSchwarze0: Introduce a common base image for all supporting steps

#1266 by @​SaschaSchwarze0: You can now define a securityContext on build strategy level to control the runAs user for all steps including the shipwright-managed steps. This allows you to use any runAs user for your build strategy steps while still being able to run without any runAsRoot steps.

#1235 by @​qu1queee: API additions: Introduce Shipwright Build v1beta1 API types

#1046 by @​SaschaSchwarze0: Shipwright is now capable of pushing the image built by the strategy steps to the container registry

Fixes

#1407 by @​qu1queee: Downgrade k8s.io/utils/ptr to k8s.io/utils/pointer due to dependency conflicts with controller-runtime pkg

#1390 by @​isibeni: The logic to detect whether a BuildRun failed due to an evicted Pod was improved

#1277 by @​SaschaSchwarze0: The platform support for the ko build strategy is functional again

#1239 by @​mjgallag: Fix buildkit cluster build strategy's cache import from insecure registry.

#1219 by @​SaschaSchwarze0: The ko sample build strategy now makes the source directory a Git safe directory so that Go builds can retrieve version control information

#1176 by @​HeavyWombat: The Git source step of a build strategy now returns a more elaborate error in case basic authentication (username and password) are used in combination with a HTTP URI. Instead of a generic error, an error message with an explanation is presented to be more clear and helpful. Also, inline credentials used in the URL will be redacted in the log output.

#1156 by @​dalbar: Fixes cancelation of buildruns without a build reference.

API Changes

#1403 by @​qu1queee: Add conversion logic for local type of sources. BuildRun CRs now support a .spec.source object that can only be of the type Local. Build CRs now make it explicit on support for the .spec.source of the type Local.

#1266 by @​SaschaSchwarze0: You can now define a securityContext on build strategy level to control the runAs user for all steps including the shipwright-managed steps. This allows you to use any runAs user for your build strategy steps while still being able to run without any runAsRoot steps.

#1235 by @​qu1queee: API additions: Introduce Shipwright Build v1beta1 API types

#1046 by @​SaschaSchwarze0: Shipwright is now capable of pushing the image built by the strategy steps to the container registry

... (truncated)

Commits


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

openshift-ci[bot] commented 1 year ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign otaviof for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/shipwright-io/triggers/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
SaschaSchwarze0 commented 1 year ago

@dependabot rebase

openshift-merge-robot commented 1 year ago

rebase

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.