Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update module github.com/open-policy-agent/opa to v0.61.0 - autoclosed #118

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 10, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/open-policy-agent/opa v0.49.2 -> v0.61.0 age adoption passing confidence

Release Notes

open-policy-agent/opa (github.com/open-policy-agent/opa)

v0.61.0

Compare Source

This release contains a mix of new features and bugfixes.

Runtime, SDK
Topdown
Docs
Miscellaneous
  • linters+testdata: Reformat all yaml testcases for linting. (#​6511) authored by @​philipaconrad
  • Dependency updates, notably:
    • bump github.com/containerd/containerd from 1.7.11 to 1.7.12
    • bump github.com/go-logr/logr from 1.3.0 to 1.4.1
    • bump github.com/google/uuid from 1.5.0 to 1.6.0
    • bump github.com/prometheus/client_golang from v1.16.0 to v1.18.0
    • bump google.golang.org/grpc from 1.60.1 to 1.61.0

v0.60.0

Compare Source

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
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

Compare Source

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:

  • 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).
  • deprecated built-in functions will be removed.

This current release (0.59.0) introduces a new --rego-v1 flag to the opa fmt and opa check commands to facilitate the transition of existing policies to be compatible with the 1.0 syntax.

When used with opa fmt, the --rego-v1 flag will format the module(s) according to the new Rego syntax in OPA 1.0.
Formatted modules are compatible with both the current version of OPA and 1.0.
Modules using deprecated built-ins will terminate formatting with an error. Future versions of OPA will support rewriting applicable function calls with equivalent Rego compatible with 1.0.

When used with opa check, the --rego-v1 flag will check that the modules are compatible with both the current version of OPA and 1.0.

Relevant Changes
Runtime, Tooling, SDK
Topdown and Rego
Miscellaneous

v0.58.0

Compare Source

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.

This release contains a mix of performance improvements, bugfixes and security fixes for third-party libraries.

Runtime, Tooling, SDK
  • cmd/test: Display lines not covered if code coverage threshold not met in verbose reporting mode (#​2562) authored by @​johanfylling
  • cmd/test: Don't round up test coverage calculation as it could lead to inaccurate code coverage results (#​6307) authored by @​anderseknert
  • cmd/fmt: Don't format functions without a value to include = true as it is implied (#​6323) authored by @​anderseknert
  • server: Remove deprecated partial query parameter from REST API. This option has been deprecated since v0.23.0 (#​2266) authored by @​ashutosh-narkar
  • Add support for configurable prometheus buckets for the http_request_duration_seconds metric (#​6238) authored by @​AdrianArnautu
  • plugins/bundle: Update bundle plugin state on a reconfigure operation when existing bundle is not modified (#​6311) authored by @​asadk12
  • internal/pathwatcher: Fix how paths to watch by a fsnotify watcher are determined to avoid monitoring unintended directories and files (#​6277) authored by @​ashutosh-narkar
Topdown and Rego
  • topdown: Fix issue with build optimization producing support modules with forbidden characters in first var of rule ref (#​6338) authored by @​johanfylling
  • topdown: Fix panic in build optimization when policy contains rules with a general ref in the head (#​6339) authored by @​johanfylling
  • topdown: Avoid unnecessary conversion of small numbers by caching them and thereby helping to speed up some arithmetic operations (#​6021) authored by @​ashutosh-narkar
  • ast+rego: Disable compiler stages for IR-based eval paths (#​6335) authored by @​srenatus
  • built-in/walk: Skip path creation if path is assigned a wildcard to achieve faster walk-ing (#​6267) authored by @​anderseknert
  • ast: Add regression test for edge case where partial rule hides recursion cycle (#​6318) authored by @​johanfylling
Docs
  • Drop EXPERIMENTAL status of reported prom metrics (#​6298) authored by @​ashutosh-narkar
  • Update documentation on GCS bundles for case where the resource (the object in the GCS bucket) contains slashes (/) or other special characters (#​6264) authored by @​dennisg
  • Provide a more clear description of negation in the policy language section (#​6275) authored by @​gusega
Website + Ecosystem
  • Fix un-versioned built-in docs issue so that only the built-ins for a given doc version are displayed (#​6269) authored by @​charlieegan3
Miscellaneous
  • ci: Remove hub tool in GitHub workflows in favor of GitHub CLI tool (#​6326) authored by @​ashutosh-narkar
  • Dependency updates; notably:
    • bump go.opentelemetry.io modules (#​6292) authored by @​cksidharthan
    • aquasecurity/trivy-action from 0.12.0 to 0.13.0
    • github.com/containerd/containerd from 1.7.6 to 1.7.7
    • github.com/fsnotify/fsnotify from 1.6.0 to 1.7.0
    • golang.org/x/net from 0.15.0 to 0.17.0
    • google.golang.org/grpc from 1.58.2 to 1.59.0 (addresses vulnerability GHSA-m425-mq94-257g)
    • oras.land/oras-go/v2 from 2.3.0 to 2.3.1
    • sigs.k8s.io/yaml from 1.3.0 to 1.4.0

v0.57.1

Compare Source

This is a bug fix release addressing the following security issues:

Golang security fix GO-2023-2102

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption.

OpenTelemetry-Go Contrib security fix CVE-2023-45142

Denial of service in otelhttp due to unbound cardinality metrics.

v0.57.0

Compare Source

This release contains an updated Rego syntax to allow general references in rule heads, and a mix of new features and bugfixes.

Support for General References in Rule Heads

In OPA 0.56.0, we introduced support for general references in rule heads as an experimental feature.
It has now graduated to a fully supported feature, and is no longer experimental.

A general reference is a reference with variables at arbitrary locations.
In Rego, partial rules are used for generating sets and objects.
In previous versions of OPA, variables were only allowed in the very last position in the rule's reference.
Now, Rego has been expanded to allow rules to be declared with general references in their head, with variables at arbitrary locations.
This allows for generating nested dynamic object structures:

package example

import future.keywords

### Converting a flat list of users to a mapping by "role" and then "id".
users_by_role[role][id] := user if {
    some user in data.users
    id := user.id
    role := user.role
}

### Explicit "admin" key override to the above mapping.
users_by_role.admin[id] := user if {
    some user in data.admins
    id := user.id
}

### Leaf entries can be multi-value.
users_by_country[country] contains user.id if {
    some user in data.users
    country := user.country
}

See the documentation for more information.

Authored by @​johanfylling.

Runtime, Tooling, SDK
Topdown and Rego
Miscellaneous
Breaking Changes

GO SDK: the ast.JSONOptions struct has changed location to ast.json.Options.

v0.56.0

Compare Source

This release contains a mix of new features, bugfixes and a new builtin function.

Support for General References in Rule Heads (Experimental)

A new experimental feature in OPA is support for general refs in rule heads. Where a general ref is a reference with variables at arbitrary locations.

package example

import future.keywords

### Converting a flat list of users to a mapping by "role" and then "id".
users_by_role[role][id] := user if {
    some user in data.users
    id := user.id
    role := user.role
}

### Explicit "admin" key override to the above mapping.
users_by_role.admin[id] := user if {
    some user in data.admins
    id := user.id
}

### Leaf entries can be multi-value.
users_by_country[country] contains user.id if {
    some user in data.users
    country := user.country
}

General refs are currently not supported by the OPA planner, making this feature unsupported for Wasm and IR.

Note: this feature is disabled by default, and needs to be enabled by setting the EXPERIMENTAL_GENERAL_RULE_REFS environment variable (once the feature is complete - supports Wasm and IR - this requirement will be dropped).

Authored by @​johanfylling.

New Built-In Function: numbers.range_step

Similar to the numbers.range built-in function, numbers.range_step returns an array of numbers in a given range. The new built-in function also allows you to control the step between each entry.

See the documentation on the new built-in
for all the details.

Authored by @​sspaink.

New Ecosystem page on The Website

The OPA Ecosystem of related integrations has been refreshed and moved to a more prominent location on the website.

If you're interested to add any new integrations you've been working on, please see the docs here (updates to existing integrations are very welcome too!).

Runtime, Tooling, SDK
Topdown and Rego
Miscellaneous
Breaking changes

Since its introduction in 0.34.0, the --exit-zero-on-skipped option always made the opa test command return an exit code 0. When used, it now returns the exit code 0 only if no failed tests were found.

Test runs on existing projects using --exit-zero-on-skipped will fail if any failed tests were inhibited by this behavior.

v0.55.0

Compare Source

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 be 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.

  • The minimum version of Go required to build the OPA module is 1.19

This release contains a mix of new features, bugfixes and a new builtin function.

Honor default keyword on functions

Previously if a function was defined with a default value, OPA would ignore it. Now the default function is honored
if all functions with the same name are undefined. For example,

package example

default clamp_positive(_) := 0

clamp_positive(x) = x {
    x > 0
}
$ opa eval -d example.rego 'data.example.clamp_positive(1)' -f pretty
1
$ opa eval -d example.rego 'data.example.clamp_positive(-1)' -f pretty
0

The value of a default function follows the same conditions as that of a default rule. In addition, a default
function satisfies the following properties:

  • same arity as other functions with the same name
  • arguments should only be plain variables ie. no composite values
  • argument names should not be repeated

NOTE:

default functions used to be previously ignored. If existing policies contain default functions, ensure that they conform
to the properties mentioned above. Otherwise, those policies will fail to evaluate.

Authored by @​ashutosh-narkar.

New Built-In Function: crypto.parse_private_keys

crypto.parse_private_keys returns zero or more private keys from the given encoded string containing DER certificate data.
If the input contains a list of one or more concatenated PEM blocks, then the built-in will output the parsed private keys
represented as objects.

See the documentation on the new built-in
for all the details.

Authored by @​volck.

Runtime, Tooling, SDK
  • plugins/rest: Add AWS KMS support for OAuth2 Client Credentials JWT authentication (#​5942) authored by @​prasanthu
  • sdk: Update input object to conform to the format expected by decision log masking (#​6090) authored by @​epaulson10
  • sdk: Add option for specifying decision ID to SDK. Users can use this to control the ID that gets included in the decision logs (#​6101) authored by @​brianchhun-chime
  • cmd: Add discard output format to opa eval which discards the result while still showing the output of eval flags like --profile (#​6103) authored by @​26tanishabanik
  • Make rootless deprecation messages more explicit as all published OPA images now run with non-root uid/gid (#​6091) authored by @​charlieegan3
  • download/oci: Add support for Docker Registry v2 authentication scheme (#​6045) authored by @​gitu and @​DerGut
  • plugins/discovery: Ensure discovery plugin doesn't erase its own config on the plugin manager (#​6070) authored by @​blacksails
Topdown and Rego
  • ast: Add WithRoots compiler option that allows callers to set the roots to include in the output bundle manifest (#​6088) authored by @​kubaj
  • rego: Parse store modules iff modules set on the Rego object. This change assumes that while using the Rego package, the compiler and store are kept in-sync, and thereby attempts to avoid a race during the compilation process (#​6081) authored by @​ashutosh-narkar
Docs
Website + Ecosystem
Miscellaneous
  • chore: Update comments on some exported functions and clean up instances where the same package was imported multiple times (authored by @​testwill)
  • Fix issue in the OPA release patch scripts related to CRLF line terminations in the patch output (#​6069) authored by @​johanfylling
  • Dependency bumps, notably:
    • golang from 1.20.5 to 1.20.6
    • oras.land/oras-go/v2 from 2.2.0 to 2.2.1
    • google.golang.org/grpc from 1.56.1 to 1.56.2
    • github.com/containerd/containerd from 1.6.19 to 1.7.2
    • golang.org/x/net from 0.11.0 to 0.12.0
    • go.uber.org/automaxprocs from 1.5.2 to 1.5.3
    • go.opentelemetry.io/otel from v1.14.0 to v1.16.0 (#​6062) authored by @​srenatus with feedback from @​ghaskins and @​zregvart

v0.54.0

Compare Source

This release focuses on bug fixes, but also includes some improvements to the SDK and commandline.

Note: This will be the last OPA release to support building with Golang 1.18. (Golang 1.21 is expected to be released in August. Keeping the support for 1.18 is blocking OPA from upgrading OpenTelemetry.)

Topdown and Rego
Runtime, Tooling, SDK
Miscellaneous

v0.53.1

Compare Source

This is a bug fix release addressing the following issues:

Runtime, Tooling, SDK
  • plugins/logs: Previously while passing the decision log plugins's status to the Status API, the plugin held the mutex while a status upload was in process. This had the potential to block new decisions from being written to the plugin's buffer. To avoid this situation, a local copy of plugin's status is created (#​5966) authored by @​ashutosh-narkar
  • download: Public docker repositories require an authorization handshake where the client needs to respond to challenges marked by the WWW-Authenticate header of a 401 Unauthorized response. Errors were returned when downloading a public image as it was assumed that authorization is not necessary for public repositories. This fix addresses this issue by challenging any 401 Unauthorized responses by passing it to the docker.Authorizer (#​5902) authored by @​DerGut
  • opa fmt: Fix panic encountered while processing policies with comprehensions written on multiple lines with comments in these lines (#​5798) authored by @​Trolloldem
Topdown and Rego
  • built-in function object.subset: Fix an issue in object.subset related to incorrect results being generated when arrays are provided as an input (#​5968) authored by @​DCRUNNN
  • planner: Fix the optimization check for overlapping ref rules (#​5964) authored by @​srenatus

v0.53.0

Compare Source

This release contains some enhancements, bugfixes, and a new builtin function.

Runtime, Tooling, SDK
  • status: Ensure Status plugin is correctly reconfigured to register or unregister Prometheus Collectors based on the state provided in OPA's active config (#​5918) authored by @​johanfylling
  • opa eval: Update OPA eval's --profile-sort flag description to highlight the valid options to sort the profile results (#​5924) authored by @​ecbenezra
  • opa fmt: Fix cases in which invalid code was generated due to parentheses being improperly handled (#​5537) authored by @​Trolloldem
  • rest: Allow users to configure the AWS STS domain when using Web Identity Credentials (#​5915) authored by @​johanfylling
  • status: Add an OPA environment information Gauge to Prometheus metrics to capture information like OPA version (#​5852) authored by @​jmoghisi
  • server: Add ability to configure Unix socket permissions if OPA is listening on a Unix socket (#​5888) authored by @​ashutosh-narkar
  • loader: Allow extensions to the loader package that provide ability to register handlers for certain file extensions. This feature is currently EXPERIMENTAL (#​5940) authored by @​srenatus
Topdown and Rego
  • New built-in function crypto.x509.parse_keypair: Returns a key pair from a pair of PEM or base64 encoded strings of data. See the documentation on the new built-in for all the details. (#​5853) authored by @​volck.
  • ast: Abort query evaluation if the compiler has errors. These errors will be exposed via the Status API if enabled (#​5947) authored by @​johanfylling
  • io.jwt.decode_verify: Fix issue where token verification succeeded in case where iss constraint was required but JWT did not contain it (#​5850) authored by @​AleksanderBrzozowski
  • wasm: Fix memory leaks in WASM when incrementally adding or removing data (#​5785) and (#​5901) authored by @​ctelfer-sophos
  • http.send: Add a new option to the http.send input object which allows policy authors to specify a retry count for executing a HTTP request. Retries are performed with an exponential backoff delay (#​5891) authored by @​ashutosh-narkar
  • ast: Fix issue with _ matching only scalars in rule indexing for arrays (#​5916) authored by @​jaspervdj
  • rego: Allow for extending the Rego evaluation targets with plugins (#​5939) authored by @​srenatus
Miscellaneous
  • Add PITS Global Data Recovery Services to ADOPTERS.md (authored by @​pheianox)
  • Avoid unnecessary byte/string conversion by using alternative functions/methods (#​5944) authored by @​Juneezee
  • False positive finding of CVE-2022-3517 addressed by removing the dead code (#​5941) authored by @​testwill
  • Dependency bumps, notably:
    • golang from 1.20.3 to 1.20.4
    • golang.org/x/net from 0.9.0 to 0.10.0
    • google.golang.org/grpc from 1.54.0 to 1.55.0
    • oras.land/oras-go/v2 from 2.0.2 to 2.2.0
    • github.com/prometheus/client_golang from 1.15.0 to 1.15.1

v0.52.0

Compare Source

This release contains some enhancements, bugfixes, and a new builtin function.

Allow Adding Labels via Discovery

Previously OPA did not allow any updates to the labels provided in the boot configuration via the discovered (ie. service)
config. This was done to avoid breaking the discovery configuration. But there are use cases where labels can serve as a convenient
way to pass information that could be used in policies, status updates or decision logs. This change allows
additional labels to be configured in the service config which are then made available during runtime.

See the Discovery documentation for more details.

Authored by @​mjungsbluth.

New Built-In Function: crypto.hmac.equal

crypto.hmac.equal provides a convenie


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.50.0 Update module github.com/open-policy-agent/opa to v0.50.1 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch 2 times, most recently from edf7f3e to 0c4d9c9 Compare March 21, 2023 15:18
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.50.1 Update module github.com/open-policy-agent/opa to v0.50.2 Mar 21, 2023
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.50.2 Update module github.com/open-policy-agent/opa to v0.51.0 Mar 31, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 0c4d9c9 to b48d1b7 Compare March 31, 2023 15:21
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from b48d1b7 to 47f0e6c Compare April 27, 2023 21:18
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.51.0 Update module github.com/open-policy-agent/opa to v0.52.0 Apr 27, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 47f0e6c to 98babda Compare May 28, 2023 11:08
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.52.0 Update module github.com/open-policy-agent/opa to v0.53.0 May 28, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 98babda to 9252ffe Compare June 6, 2023 09:11
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.53.0 Update module github.com/open-policy-agent/opa to v0.53.1 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 9252ffe to 2714657 Compare June 29, 2023 20:43
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.53.1 Update module github.com/open-policy-agent/opa to v0.54.0 Jun 29, 2023
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.54.0 Update module github.com/open-policy-agent/opa to v0.55.0 Jul 27, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 2714657 to 295b94d Compare July 27, 2023 21:23
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 295b94d to 8e1818b Compare August 31, 2023 15:22
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.55.0 Update module github.com/open-policy-agent/opa to v0.56.0 Aug 31, 2023
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.56.0 Update module github.com/open-policy-agent/opa to v0.57.0 Sep 28, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 8e1818b to 73afb51 Compare September 28, 2023 14:46
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.57.0 Update module github.com/open-policy-agent/opa to v0.57.1 Oct 18, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 73afb51 to 32e2d48 Compare October 18, 2023 10:50
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 32e2d48 to df5e562 Compare October 27, 2023 01:44
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.57.1 Update module github.com/open-policy-agent/opa to v0.58.0 Oct 27, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from df5e562 to c7657a6 Compare November 30, 2023 16:41
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.58.0 Update module github.com/open-policy-agent/opa to v0.59.0 Nov 30, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch 2 times, most recently from d0c0d89 to 3b0e891 Compare December 21, 2023 01:53
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.59.0 Update module github.com/open-policy-agent/opa to v0.60.0 Dec 21, 2023
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 3b0e891 to ed2bc92 Compare January 25, 2024 14:28
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.60.0 Update module github.com/open-policy-agent/opa to v0.61.0 Jan 25, 2024
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from ed2bc92 to 2f41c5d Compare February 5, 2024 06:59
@renovate renovate bot force-pushed the renovate/github.com-open-policy-agent-opa-0.x branch from 2f41c5d to 9ef21b8 Compare February 5, 2024 07:43
@renovate renovate bot changed the title Update module github.com/open-policy-agent/opa to v0.61.0 fix(deps): update module github.com/open-policy-agent/opa to v0.61.0 Feb 5, 2024
@renovate renovate bot changed the title fix(deps): update module github.com/open-policy-agent/opa to v0.61.0 fix(deps): update module github.com/open-policy-agent/opa to v0.61.0 - autoclosed Feb 5, 2024
@renovate renovate bot closed this Feb 5, 2024
@renovate renovate bot deleted the renovate/github.com-open-policy-agent-opa-0.x branch February 5, 2024 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant