Bump the backend group with 3 updates

[dependabot]

Bumps the backend group with 3 updates: github.com/open-policy-agent/opa, github.com/tektoncd/pipeline and google.golang.org/api.

Updates github.com/open-policy-agent/opa from 0.58.0 to 0.60.0

Release notes

Sourced from github.com/open-policy-agent/opa's releases.

v0.60.0

Runtime, Tooling, SDK

• OPA can be run in 1.0 compatibility mode by using the new --v1-compatible flag. When this mode is enabled, the current release of OPA will behave as OPA v1.0 will eventually behave by default. This flag is currently supported on the build, check, fmt, eval and test commands (#6478) authored by @​johanfylling
• Extend the telemetry report to include the minimum compatible version of policies loaded into OPA (#6361) co-authored by @​srenatus and @​ashutosh-narkar
• server: Support fsnotify based reloading of certificate, key and CA cert pool when they change on disk (#5788) authored by @​charlieegan3
• Add option on the unit test runner to surface builtin errors. This should help with debugging errors generated while running unit tests (#6489) authored by @​jalseth
• Fix issue in opa fmt where the assignment operator and term in the rule head of chain rules are removed from the re-written rule head (#6467) authored by @​anderseknert
• cmd/fmt: Replace dependency on diff tool with an external golang library function (#6284) authored by @​colinjlacy

Topdown and Rego

• topdown/providers: Preserve user provided http headers in the providers.aws.sign_req builtin command (#6456) authored by @​c2zwdjnlcg
• rego: Allow custom builtin function registration to provide a description for the builtin (#6449) authored by @​lcarva
• ast+cmd: Allow bundle to contain calls to unknown functions when inspected (#6457) authored by @​johanfylling

Docs

• Add section on the changes proposed for a future OPA v1.0 and update Rego examples to be OPA v1.0 compliant(#6453) authored by @​johanfylling
• Clarify behavior of the sprintf builtin command when used with the %T marker (#6487) authored by @​lcarva

Website + Ecosystem

• Ecosystem: Digger (#6464) authored by @​anderseknert

Miscellaneous

• Update Makefile to allow custom GOFLAGS to be provided to the golang executable (#6458) authored by @​cova-fe
• Dependency updates; notably:
  • bump golang 1.21.4 -> 1.21.5 (#6460) authored by @​srenatus
  • bump aquasecurity/trivy-action from 0.14.0 to 0.16.0
  • bump github.com/containerd/containerd from 1.7.9 to 1.7.11
  • bump google.golang.org/grpc from 1.59.0 to 1.60.1
  • bump github.com/google/uuid from 1.4.0 to 1.5.0

v0.59.0

This release adds tooling to help prepare existing policies for the upcoming OPA 1.0 release. It also contains a mix of improvements, bugfixes and security fixes for third-party libraries.

NOTES:

• All published OPA images now run with a non-root uid/gid. The uid:gid is set to 1000:1000 for all images. As a result there is no longer a need for the -rootless image variant and hence it will not be published as part of future releases. This change is in line with container security best practices. OPA can still be run with root privileges by explicitly setting the user, either with the --user argument for docker run, or by specifying the securityContext in the Kubernetes Pod specification.

Rego v1

The upcoming release of OPA 1.0, which will be released at a future date, will introduce breaking changes to the Rego language. Most notably:

... (truncated)

Changelog

Sourced from github.com/open-policy-agent/opa's changelog.

0.60.0

Runtime, Tooling, SDK

• OPA can be run in 1.0 compatibility mode by using the new --v1-compatible flag. When this mode is enabled, the current release of OPA will behave as OPA v1.0 will eventually behave by default. This flag is currently supported on the build, check, fmt, eval and test commands (#6478) authored by @​johanfylling
• Extend the telemetry report to include the minimum compatible version of policies loaded into OPA (#6361) co-authored by @​srenatus and @​ashutosh-narkar
• server: Support fsnotify based reloading of certificate, key and CA cert pool when they change on disk (#5788) authored by @​charlieegan3
• Add option on the unit test runner to surface builtin errors. This should help with debugging errors generated while running unit tests (#6489) authored by @​jalseth
• Fix issue in opa fmt where the assignment operator and term in the rule head of chain rules are removed from the re-written rule head (#6467) authored by @​anderseknert
• cmd/fmt: Replace dependency on diff tool with an external golang library function (#6284) authored by @​colinjlacy

Topdown and Rego

• topdown/providers: Preserve user provided http headers in the providers.aws.sign_req builtin command (#6456) authored by @​c2zwdjnlcg
• rego: Allow custom builtin function registration to provide a description for the builtin (#6449) authored by @​lcarva
• ast+cmd: Allow bundle to contain calls to unknown functions when inspected (#6457) authored by @​johanfylling

Docs

• Add section on the changes proposed for a future OPA v1.0 and update Rego examples to be OPA v1.0 compliant(#6453) authored by @​johanfylling
• Clarify behavior of the sprintf builtin command when used with the %T marker (#6487) authored by @​lcarva

Website + Ecosystem

• Ecosystem: Digger (#6464) authored by @​anderseknert

Miscellaneous

• Update Makefile to allow custom GOFLAGS to be provided to the golang executable (#6458) authored by @​cova-fe
• Dependency updates; notably:
  • bump golang 1.21.4 -> 1.21.5 (#6460) authored by @​srenatus
  • bump aquasecurity/trivy-action from 0.14.0 to 0.16.0
  • bump github.com/containerd/containerd from 1.7.9 to 1.7.11
  • bump google.golang.org/grpc from 1.59.0 to 1.60.1
  • bump github.com/google/uuid from 1.4.0 to 1.5.0

0.59.0

This release adds tooling to help prepare existing policies for the upcoming OPA 1.0 release. It also contains a mix of improvements, bugfixes and security fixes for third-party libraries.

NOTES:

• All published OPA images now run with a non-root uid/gid. The uid:gid is set to 1000:1000 for all images. As a result there is no longer a need for the -rootless image variant and hence it will not be published as part of future releases. This change is in line with container security best practices. OPA can still be run with root privileges by explicitly setting the user, either with the --user argument for docker run, or by specifying the securityContext in the Kubernetes Pod specification.

Rego v1

The upcoming release of OPA 1.0, which will be released at a future date, will introduce breaking changes to the Rego language. Most notably:

• the keywords that currently must be imported through import future.keywords into a module before use will be part of the Rego language by default, without the need to first import them.
• the if keyword will be required before the body of a rule.
• the contains keyword will be required when declaring a multi-value rule (partial set rule).

... (truncated)

Commits

• a1a2ae3 Prepare v0.60.0 release
• 9f63fdb ast+cmd: Allowing bundle to contain calls to unknown functions when inspected...
• f04636a docs: Update generated CLI docs
• 38c2f0c Adding --v1-compatible flag to build, opa eval (#6478)
• 84751f0 build(deps): bump google.golang.org/grpc from 1.60.0 to 1.60.1
• 979e626 internal/presentation: cleanup location handling (#6498)
• b85eb64 .github/workflows: Update name of the checkout action token
• 24f09cd .github/workflows: Update checkout action token
• ba46112 Docs: Explain %T behavior of sprintf
• 6d26f98 feat: Support raising builtin errors in the test runner
• Additional commits viewable in compare view

Updates github.com/tektoncd/pipeline from 0.53.2 to 0.55.0

Release notes

Sourced from github.com/tektoncd/pipeline's releases.

Tekton Pipeline release v0.55.0 "Bambino Alojzy Gąbka"

🎉 PipelineTask.OnError and bugfixes 🎉

-Docs @ v0.55.0 -Examples @ v0.55.0

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.55.0/release.yaml

Attestation

The Rekor UUID for this release is 24296fb24b8ad77acf6e7f5cf38da4c2178e88e08bc2f291dc52b756371a21d349ca985bd125ace9

Obtain the attestation:

REKOR_UUID=24296fb24b8ad77acf6e7f5cf38da4c2178e88e08bc2f291dc52b756371a21d349ca985bd125ace9
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .

Verify that all container images in the attestation are in the release file:

RELEASE_FILE=https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.55.0/release.yaml
REKOR_UUID=24296fb24b8ad77acf6e7f5cf38da4c2178e88e08bc2f291dc52b756371a21d349ca985bd125ace9
Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.55.0@sha256:" + .digest.sha256')
Download the release file
curl "$RELEASE_FILE" > release.yaml
For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done

Changes

Features

• ✨ TEP-0142: Introduce WorkingDir in StepActions (#7461)

Introduce WorkingDir in StepActions

... (truncated)

Changelog

Sourced from github.com/tektoncd/pipeline's changelog.

Tekton Pipeline Releases

Release Frequency

Tekton Pipelines follows the Tekton community [release policy][release-policy] as follows:

• Versions are numbered according to semantic versioning: vX.Y.Z
• A new release is produced on a monthly basis
• Four releases a year are chosen for long term support (LTS). All remaining releases are supported for approximately 1 month (until the next release is produced)
  • LTS releases take place in January, April, July and October every year
  • The first Tekton Pipelines LTS release will be v0.41.0 in October 2022
  • Releases happen towards the middle of the month, between the 13th and the 20th, depending on week-ends and readiness

Tekton Pipelines produces nightly builds, publicly available on gcr.io/tekton-nightly.

Transition Process

Before release v0.41 Tekton Pipelines has worked on the basis of an undocumented support period of four months, which will be maintained for the releases between v0.37 and v0.40.

Release Process

Tekton Pipeline releases are made of YAML manifests and container images. Manifests are published to cloud object-storage as well as [GitHub][tekton-pipeline-releases]. Container images are signed by [Sigstore][sigstore] via [Tekton Chains][tekton-chains]; signatures can be verified through the [public key][chains-public-key] hosted by the Tekton Chains project.

Further documentation available:

• The Tekton Pipeline [release process][tekton-releases-docs]
• [Installing Tekton][tekton-installation]
• Standard for [release notes][release-notes-standards]

Release

v0.54

• Latest Release: [v0.54.0][v0.54-0] (2023-11-27) ([docs][v0.54-0-docs], [examples][v0.54-0-examples])
• Initial Release: [v0.54.0][v0.54-0] (2023-11-27)
• Estimated End of Life: 2023-12-27
• Patch Releases: [v0.54.0][v0.54-0]

... (truncated)

Commits

• e59ee42 Error sweep: complete user-facing error messages formats
• 36de579 Fix showing error message when validation fail
• c43d040 Add stdoutConfig and stderrConfig to alpha features table
• 218b6b2 Bump github.com/spiffe/spire-api-sdk from 1.8.4 to 1.8.5
• a7ab091 Fix step actions documentation
• 7a9f4c3 Freeze image sha for dind-sidecar example test.
• e8d3bfd [TEP-0131] Update Conformance Spec for v1 api types
• 5e3b0dc TEP-0142: Introduce WorkingDir in StepActions
• 8e9fd46 Fix enum validation with multiple param references
• 5c47c88 FIX: Prevent panic on parameter evaluation
• Additional commits viewable in compare view

Updates google.golang.org/api from 0.153.0 to 0.154.0

Release notes

Sourced from google.golang.org/api's releases.

v0.154.0

0.154.0 (2023-12-12)

Features

• all: Auto-regenerate discovery clients (#2293) (cefa0cd)
• all: Auto-regenerate discovery clients (#2294) (c059038)
• all: Auto-regenerate discovery clients (#2295) (161a8e5)
• all: Auto-regenerate discovery clients (#2297) (e5e778a)
• all: Auto-regenerate discovery clients (#2298) (d27a8e0)
• all: Auto-regenerate discovery clients (#2300) (be0daf0)
• transport: Add OpenTelemetry context propagation (#2127) (46421d4)

Changelog

Sourced from google.golang.org/api's changelog.

0.154.0 (2023-12-12)

Features

• all: Auto-regenerate discovery clients (#2293) (cefa0cd)
• all: Auto-regenerate discovery clients (#2294) (c059038)
• all: Auto-regenerate discovery clients (#2295) (161a8e5)
• all: Auto-regenerate discovery clients (#2297) (e5e778a)
• all: Auto-regenerate discovery clients (#2298) (d27a8e0)
• all: Auto-regenerate discovery clients (#2300) (be0daf0)
• transport: Add OpenTelemetry context propagation (#2127) (46421d4)

Commits

• 08bc733 chore(main): release 0.154.0 (#2292)
• 861bc79 chore(all): update module github.com/google/go-github/v52 to v57 (#2289)
• be0daf0 feat(all): auto-regenerate discovery clients (#2300)
• 432541d chore(all): update all (#2288)
• d27a8e0 feat(all): auto-regenerate discovery clients (#2298)
• e5e778a feat(all): auto-regenerate discovery clients (#2297)
• 161a8e5 feat(all): auto-regenerate discovery clients (#2295)
• c059038 feat(all): auto-regenerate discovery clients (#2294)
• cefa0cd feat(all): auto-regenerate discovery clients (#2293)
• 46421d4 feat(transport): add OpenTelemetry context propagation (#2127)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.