build(deps): Bump github.com/open-policy-agent/opa from 1.20.1 to 1.20.2 in /authbridge/authlib

[dependabot]

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

Release notes

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

v1.20.2

This release includes a bug fix for a parser regression introduced in v1.20.0, and dependency updates.

Fix stale parse errors on statements starting with { (#9140)

When the and/or keywords added in v1.20.0 are imported, a statement that starts with { is first read as an explicit operand body, and re-read as a term (a comprehension, for example) if no and or or follows. Errors recorded during the abandoned first attempt stayed in the parser's term cache and were reported against the successful re-read, rejecting policies that parse fine:

package example
import future.keywords
xs := [1, 2, 3]
allow if {
{
y |
some y in xs # rego_parse_error: unexpected some keyword
} == {1, 2, 3}
}

The term cache is now restored along with the rest of the parser state when the operand-body guess is abandoned. Only policies importing and or or — directly or via import future.keywords — were affected; policies that don't import them parse unchanged.

Authored by @​sspaink

Miscellaneous

• build(go): Bump to 1.27.1 (3652eeb) authored by @​srenatus
• Dependency updates; notably:
  • build(deps): Bump github.com/dgraph-io/badger/v4 from 4.9.5 to 4.9.6
  • build(deps): Bump github.com/lestrrat-go/jwx/v3 from 3.1.1 to 3.2.0
  • build(deps): Bump github.com/santhosh-tekuri/jsonschema/v6 from 6.0.2 to 6.0.3
  • build(deps): Bump github.com/sirupsen/logrus from 1.9.4 to 1.10.2
  • build(deps): Bump go.opentelemetry.io/contrib/bridges/prometheus from 0.69.0 to 0.71.0
  • build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.69.0 to 0.71.0
  • build(deps): Bump go.opentelemetry.io/otel from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/sdk from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/sdk/metric from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/trace from 1.44.0 to 1.46.0

... (truncated)

Changelog

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

1.20.2

This release includes a bug fix for a parser regression introduced in v1.20.0, and dependency updates.

Fix stale parse errors on statements starting with { (#9140)

When the and/or keywords added in v1.20.0 are imported, a statement that starts with { is first read as an explicit operand body, and re-read as a term (a comprehension, for example) if no and or or follows. Errors recorded during the abandoned first attempt stayed in the parser's term cache and were reported against the successful re-read, rejecting policies that parse fine:

package example
import future.keywords
xs := [1, 2, 3]
allow if {
{
y |
some y in xs # rego_parse_error: unexpected some keyword
} == {1, 2, 3}
}

The term cache is now restored along with the rest of the parser state when the operand-body guess is abandoned. Only policies importing and or or — directly or via import future.keywords — were affected; policies that don't import them parse unchanged.

Authored by @​sspaink

Miscellaneous

• build(go): Bump to 1.27.1 (3652eeb) authored by @​srenatus
• Dependency updates; notably:
  • build(deps): Bump github.com/dgraph-io/badger/v4 from 4.9.5 to 4.9.6
  • build(deps): Bump github.com/lestrrat-go/jwx/v3 from 3.1.1 to 3.2.0
  • build(deps): Bump github.com/santhosh-tekuri/jsonschema/v6 from 6.0.2 to 6.0.3
  • build(deps): Bump github.com/sirupsen/logrus from 1.9.4 to 1.10.2
  • build(deps): Bump go.opentelemetry.io/contrib/bridges/prometheus from 0.69.0 to 0.71.0
  • build(deps): Bump go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp from 0.69.0 to 0.71.0
  • build(deps): Bump go.opentelemetry.io/otel from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp from 1.44.0 to 1.46.0
  • build(deps): Bump go.opentelemetry.io/otel/sdk from 1.44.0 to 1.46.0

... (truncated)

Commits

• b2c2670 Prepare v1.20.2 release
• 0ea9844 ast: clear the term cache when a brace operand guess is abandoned (#9140)
• 04d715b build(go): bump to 1.27.1
• 17accbe build(deps): bump dependencies
• See full diff in compare view

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.