chore: bump github.com/open-policy-agent/opa from 1.4.2 to 1.20.1

[dependabot]

Bumps github.com/open-policy-agent/opa from 1.4.2 to 1.20.1.

Release notes

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

v1.20.1

This release includes a bug fix for a regression introduced in v1.20.0 in comparing a number to some float values. Thanks @​kmadan for reporting the issue and submitting a fix!

v1.20.0

This release contains a mix of new features and bug fixes. Notably:

• New Rego keywords: and and or, for combining conditions inside a single rule body
• allow_net now restricts remote JSON Schema $ref fetching from json.match_schema and json.verify_schema
• Coverage reports can now explain why a range is not covered
• Much faster partial evaluation for dynamically composed policies

New Rego keywords: and and or (#7602)

Rego gains two keywords for combining conditions inside a single rule body — a long-standing request, and one of the larger additions to the language in some time. and and or let control flow that previously had to be split across helper rules stay where it is read.

Before, a rule body that needed to succeed on one of several conditions meant extracting a rule:

package example
allow if {
input.method == "GET"
admin_or_public_owner
}
admin_or_public_owner if input.user.admin
admin_or_public_owner if {
input.user.owner
input.resource.public
}

Now:

package example
import future.keywords.and
import future.keywords.or
the and groups first, so this reads as:
an admin, or an owner of a public resource
allow if {
input.method == "GET"
</tr></table>

... (truncated)

Changelog

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

1.20.1

This release includes a bug fix for a regression introduced in v1.20.0 in comparing a number to some float values. Thanks @​kmadan for reporting the issue and submitting a fix!

1.20.0

This release contains a mix of new features and bug fixes. Notably:

• New Rego keywords: and and or, for combining conditions inside a single rule body
• allow_net now restricts remote JSON Schema $ref fetching from json.match_schema and json.verify_schema
• Coverage reports can now explain why a range is not covered
• Much faster partial evaluation for dynamically composed policies

New Rego keywords: and and or (#7602)

Rego gains two keywords for combining conditions inside a single rule body — a long-standing request, and one of the larger additions to the language in some time. and and or let control flow that previously had to be split across helper rules stay where it is read.

Before, a rule body that needed to succeed on one of several conditions meant extracting a rule:

package example
allow if {
input.method == "GET"
admin_or_public_owner
}
admin_or_public_owner if input.user.admin
admin_or_public_owner if {
input.user.owner
input.resource.public
}

Now:

package example
import future.keywords.and
import future.keywords.or
the and groups first, so this reads as:
an admin, or an owner of a public resource
allow if {
</tr></table>

... (truncated)

Commits

• 72f30d6 Prepare v1.20.1 release
• ceb4bf2 ast: fix panic comparing a decimal zero with a non-integral number (#9099)
• 328ca09 Prepare v1.20.0 release (#9095)
• ce7ab30 Add Scanara to the OPA ecosystem page. (#9094)
• cbc0993 ast: Index rules with and/or expressions (#9063)
• 54bf329 fix loading absolute paths on Windows (#9055)
• 48310c6 format: Honor line breaks before explicit and/or operand bodies (#9086)
• a3953de build/release: Create new release tool (#8959)
• ec9536c format: converge object comprehension layout (#9076)
• 255adec ast: Fix future.keywords wildcard import not including the not keyword (#...
• Additional commits viewable 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 show <dependency name> 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)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	golang/​golang.org/​x/​oauth2@​v0.29.0 ⏵ v0.36.0	+1
	golang/​github.com/​prometheus/​client_golang@​v1.22.0 ⏵ v1.24.1	+1
	golang/​golang.org/​x/​crypto@​v0.39.0 ⏵ v0.54.0	+1	+75
	golang/​golang.org/​x/​net@​v0.41.0 ⏵ v0.57.0		+3
	golang/​golang.org/​x/​tools@​v0.33.0 ⏵ v0.47.0
	golang/​github.com/​open-policy-agent/​opa@​v1.4.2 ⏵ v1.20.1	-1
	golang/​google.golang.org/​grpc@​v1.73.0 ⏵ v1.82.1	+1	+75
	golang/​google.golang.org/​protobuf@​v1.36.6 ⏵ v1.36.11	+1
	golang/​go.opentelemetry.io/​otel@​v1.37.0 ⏵ v1.44.0	+1	+16
	golang/​golang.org/​x/​text@​v0.26.0 ⏵ v0.40.0
	golang/​github.com/​prometheus/​client_model@​v0.6.1 ⏵ v0.6.2
	golang/​github.com/​prometheus/​common@​v0.63.0 ⏵ v0.70.1	-1
	golang/​golang.org/​x/​sys@​v0.33.0 ⏵ v0.47.0
	golang/​github.com/​klauspost/​compress@​v1.18.0 ⏵ v1.19.1
	golang/​github.com/​stretchr/​testify@​v1.10.0 ⏵ v1.11.1	+1
	golang/​golang.org/​x/​mod@​v0.25.0 ⏵ v0.37.0	+1
	golang/​github.com/​creack/​pty@​v1.1.21 ⏵ v1.1.24	+1
	golang/​github.com/​spf13/​pflag@​v1.0.6 ⏵ v1.0.10
	golang/​github.com/​go-jose/​go-jose/​v4@​v4.1.0 ⏵ v4.1.4		+16
	golang/​cloud.google.com/​go/​compute/​metadata@​v0.7.0 ⏵ v0.9.0	+1
	golang/​go.opentelemetry.io/​otel/​sdk@​v1.37.0 ⏵ v1.44.0	+1	+22
	golang/​github.com/​fsnotify/​fsnotify@​v1.9.0 ⏵ v1.10.1	+1
	golang/​go.opentelemetry.io/​otel/​exporters/​otlp/​otlptrace/​otlptracegrpc@​v1.35.0 ⏵ v1.44.0
	golang/​golang.org/​x/​sync@​v0.15.0 ⏵ v0.22.0
	golang/​github.com/​go-logr/​logr@​v1.4.3 ⏵ v1.4.4	+1
	golang/​go.opentelemetry.io/​otel/​trace@​v1.37.0 ⏵ v1.44.0	+1
	golang/​golang.org/​x/​term@​v0.32.0 ⏵ v0.45.0	+1
	golang/​go.opentelemetry.io/​otel/​exporters/​otlp/​otlptrace@​v1.35.0 ⏵ v1.44.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: golang github.com/envoyproxy/go-control-plane/envoy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → golang/google.golang.org/grpc@v1.82.1 → golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore golang/github.com/envoyproxy/go-control-plane/envoy@v1.37.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report