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

[dependabot]

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

Release notes

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

v1.19.0

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

• A fixed SQL injection vector in the Compile API
• Stricter safety checking for Rego assignments (:=)
• A cgo-free, faster WebAssembly runtime (wazero replaces wasmtime-go)
• Startup warnings for unknown configuration options
• A new strings.split_n built-in function
• A REPL line reader that handles pasted input correctly, migrating existing history files

Fix SQL injection vector in Compile API: Quote SQL filter field identifiers (#8945)

The field names in the SQL emitted by the Compile API come from partially evaluated refs, so a policy that selects a dynamic key — such as input.fruits[input.column] — puts caller-controlled text in an identifier position. That text was emitted verbatim, which turns

WHERE fruit.name = 'allowed'

into

WHERE fruit.name = 'allowed' OR 1=1 -- = 'allowed'

and an application appending the filter to its query returns rows the policy denies.

Field segments that are not bare identifiers are now quoted at the UCAST-to-SQL boundary, with any embedded quote character escaped. Ordinary column names stay unquoted, so existing filters keep their current shape and remain case-insensitive on Postgres.

Authored by @​thevilledev

Behavior change: stricter safety for assignment (:=) (#3546)

The assignment operator (:=) is documented as "syntactic sugar for =, local variable creation, and additional compiler checks," and the safety checker reflects that: after rewriting, := is treated identically to = (unification), so an assignment's right-hand side can be made safe by unifying "backwards" through the left-hand side. This means policies like x := y; x = 7 compile (binding y to 7) even though y is never assigned, and x := y; obj[x] can silently degrade an expected constant-time lookup into full iteration.

This change makes the right-hand-side of := be treated as a read that must be made safe by other expressions, and can no longer be satisfied through the left-hand-side. Affected policies that previously compiled now fail with a rego_unsafe_var_error. Reference iteration on the right-hand-side (e.g. some k; v := obj[k]) is unaffected.

... (truncated)

Changelog

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

1.19.0

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

• A fixed SQL injection vector in the Compile API
• Stricter safety checking for Rego assignments (:=)
• A cgo-free, faster WebAssembly runtime (wazero replaces wasmtime-go)
• Startup warnings for unknown configuration options
• A new strings.split_n built-in function
• A REPL line reader that handles pasted input correctly, migrating existing history files

Fix SQL injection vector in Compile API: Quote SQL filter field identifiers (#8945)

The field names in the SQL emitted by the Compile API come from partially evaluated refs, so a policy that selects a dynamic key — such as input.fruits[input.column] — puts caller-controlled text in an identifier position. That text was emitted verbatim, which turns

WHERE fruit.name = 'allowed'

into

WHERE fruit.name = 'allowed' OR 1=1 -- = 'allowed'

and an application appending the filter to its query returns rows the policy denies.

Field segments that are not bare identifiers are now quoted at the UCAST-to-SQL boundary, with any embedded quote character escaped. Ordinary column names stay unquoted, so existing filters keep their current shape and remain case-insensitive on Postgres.

Authored by @​thevilledev

Behavior change: stricter safety for assignment (:=) (#3546)

The assignment operator (:=) is documented as "syntactic sugar for =, local variable creation, and additional compiler checks," and the safety checker reflects that: after rewriting, := is treated identically to = (unification), so an assignment's right-hand side can be made safe by unifying "backwards" through the left-hand side. This means policies like x := y; x = 7 compile (binding y to 7) even though y is never assigned, and x := y; obj[x] can silently degrade an expected constant-time lookup into full iteration.

This change makes the right-hand-side of := be treated as a read that must be made safe by other expressions, and can no longer be satisfied through the left-hand-side. Affected policies that previously compiled now fail with a rego_unsafe_var_error. Reference iteration on the right-hand-side (e.g. some k; v := obj[k]) is unaffected.

... (truncated)

Commits

• 1e32c79 Prepare v1.19.0 release (#8955)
• db035b0 Add support for Go 1.27 & jsonv2 (#8947)
• 27fe5ce ast: Fix leaky future.keywords.not import in Rego v0 (#8953)
• ab21870 format: Keep rule body inline when the head spans multiple lines (#8904)
• 95090fa Add strings.split_n built-in function (#8915)
• 12a86ed build(deps): bump find-my-way and prisma in /e2e/api/compile/prisma
• 18815e2 build(deps): bump the dependencies group across 2 directories with 5 updates
• f1e2ac0 build(deps): bump postcss from 8.5.15 to 8.5.23 in /docs
• d9c7856 build(deps): bump js-yaml from 5.2.1 to 5.2.2 in /docs
• 69d2cc0 tester: make Result JSON round-trippable (#8946)
• 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.0	+1
	golang/​golang.org/​x/​crypto@​v0.39.0 ⏵ v0.53.0	+1	+75
	golang/​golang.org/​x/​net@​v0.41.0 ⏵ v0.56.0		+3
	golang/​golang.org/​x/​tools@​v0.33.0 ⏵ v0.47.0
	golang/​github.com/​open-policy-agent/​opa@​v1.4.2 ⏵ v1.19.0	-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.0	-1
	golang/​golang.org/​x/​sys@​v0.33.0 ⏵ v0.47.0
	golang/​github.com/​klauspost/​compress@​v1.18.0 ⏵ v1.19.0
	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