This release pulls in OPA v1.10.1.

This release pulls in OPA v1.10.0.

This release pulls in OPA v1.9.0 and the latest Regal release, v0.36.1.

The Compile API extensions have been ported from EOPA to OPA, and are now feature in EOPA as a standard OPA feature.
Concretely, this means that the headers and annotations expected for Compile API usage need to follow the OPA requirements.
If you have used EOPA's Compile API extensions to generate data filters before, you need to replace:

1. Compile metadata no longer resides in "custom section"

Before:

package filters

# METADATA
# scope: document
# custom:
#   unknowns:
#   - input.fruits
#   mask_rule: masks

After:

package filters

# METADATA
# scope: document
# compile: # <-------- replace custom with compile
#   unknowns:
#   - input.fruits
#   mask_rule: masks

(If you have other custom annotations, those can stay in the "custom" section. Only the compile-related keys have been moved into their own section.)

2. Headers

The target and dialect selection was driven by Accept headers.
Previously, these used a prefix of "application/vnd.styra".
Now, they use "application/vnd.opa", e.g. "application/vnd.opa.postgresql+json".

This release fixes a path validation bug that could cause panics when EOPA was run in server mode with --authorization=basic.

This release includes only a release engineering bugfix for the build system, with no other code changes from the EOPA v1.43.0 release.

This release pulls in OPA v1.8.0.

Until the binary signing setup is restored, we'll go with only publishing docker images (https://ghcr.io/open-policy-agent/eopa) and binaries in the GitHub release artifacts. Homebrew and properly-signed artifacts for macOS and Windows will come back in the future.