Shipwright Triggers release v0.18.0

Release changes since v0.17.0

Features

Fixes

API Changes

Docs

Misc

#172 by @SaschaSchwarze0: The Shipwright Build dependency is now at v0.18 level

Shipwright Triggers v0.17.0

Shipwright Triggers v0.17.0

This is the first official release of the Triggers project! The version number matches the minimum version of Shipwright Build it supports.

We had started Triggers back in 2022 as a way to execute Shipwright builds through Tekton's CustomRuns feature. After an initial proof of concept, the project went dormant. We have since revived it to keep the dependencies up to date, and align the project with the rest of Shipwright's release process/tooling.

Features

#161 by @adambkaplan: Add git reference as input to release pipeline workflow.

#77 by @SaschaSchwarze0: The controllers are now based on the latest versions of the PipelineRun (Tekton v1) and Build/BuildRun (Shipwright v1beta1) APIs

#59 by @SaschaSchwarze0: The shipwright-triggers deployment now satisfies the restricted PodSecurity standard

#31 by @SaschaSchwarze0: Shipwright Triggers now supports Tekton Beta CustomRuns instead of Alpha Runs

#18 by @SaschaSchwarze0: You can now specify pod placement related values through the values of the Helm chart

#12 by @otaviof: Supporting Tekton Custom-Tasks referring to Shipwright Builds, triggering BuildRuns accordingly.

#4 by @otaviof: - Tekton Pipeline support, now Builds with triggers waiting for Tekton Pipelines will be actionated- Helm Chart deployment during development and release- Application entrypoint with flags and Kubernetes liveness/readiness probes

Misc

#85 by @SaschaSchwarze0: Shipwright Triggers is now built with Go 1.21

#61 by @SaschaSchwarze0: The controller is now built with Go 1.20