Log message:
opa: Update to 1.0.0

Changes:
We are excited to announce OPA 1.0, a milestone release consolidating
an improved developer experience for the future of Policy as Code. The
release makes new functionality designed to simplify policy writing and
improve the language's consistency the default.

# Changes to Rego in OPA 1.0

Below we highlight some key changes to the defaults in OPA 1.0:

- Using if for all rule definitions and contains for multi-value rules
 is now mandatory, not just when using the rego.v1 import.
- Other new keywords (every, in) are available without any imports.
- Previously requirements that were only run in "strict mode" (like opa
  check --strict) are now the default. Duplicate imports and imports
  which shadow each other are no longer allowed.
- OPA 1.0 comes with a range of backwards compatibility features to aid
  your migrations, please see the v0 compatibility guide if you must
  continue to support v0 Rego.

For more information please see
<https://blog.openpolicyagent.org/announcing-opa-1-0-a-new-standard-for-policy-as-code-a6d8427ee828>.

Other changes:

- Improvements to memory allocations
- Wrap http.RoundTripper for SDK users
- Improvements to scientific notation parsing in units.parse
- Support customized buckets bundle_loading_duration_ns metric
- Test suite performance improvements

Log message:
opa: Update to 0.70.0

Changes:
v0.70.0
This release contains a mix of features, performance improvements, and
bugfixes.

- Optimized read mode for OPA's in-memory store

Log message:
opa: Update to 0.69.0

Changes:
v0.69.0
-------
This release contains a mix of features, bugfixes and necessary tooling
and test changes required to support the upcoming OPA `1.0` release.

- Inter-Query Value Cache

v0.68.0
-------
This release contains a mix of features and bugfixes.

- Breaking Changes: `entrypoint` annotation implies `document` scope

Log message:
Revbump all Go packages after go122 update

Log message:
Revbump all Go packages after update

Log message:
opa: Update to 0.67.1

Changes:
0.67.1
------
This is a bug fix release addressing the following issue:

- util+server: Fix bug around chunked request handling. A request
  handling caused OPA to treat all incoming chunked requests as if they
  had zero-length request bodies.

Log message:
opa: Update to 0.67.0

Changes:
v0.67.0
This release contains a mix of features, a new builtin function
(`strings.count`), performance improvements, and bugfixes.

### Breaking Change
#### Request Body Size Limits

OPA now automatically rejects very large requests.
Requests with a `Content-Length` larger than 128 MB uncompressed, and
gzipped requests with payloads that decompress to larger than 256 MB
will be rejected, as part of hardening OPA against denial-of-service
attacks. Previously, a large enough request could cause an OPA instance
to run out of memory in low-memory sidecar deployment scenarios, just
from attempting to read the request body into memory.

These changes allow improvements in memory usage for the OPA HTTP
server, and help OPA deployments avoid some accidental out-of-memory
situations.

For most users, no changes will be needed to continue using OPA.
However, to control this behavior, two new configuration keys are
available: `server.decoding.max_length` and
`server.decoding.gzip.max_length`. These control the max size in bytes
to allow for an incoming request payload, and the maximum size in bytes
to allow for a decompressed gzip request payload, respectively.

Log message:
opa: Update to 0.66.0

Changes:
v0.66.0
This release contains a mix of features, performance improvements, and bugfixes.

### Improved Test Reports

The `opa test` command now includes a new `--var-values` flag that
enriches reporting of failed tests with the values and locations for
variables in the failing expression.

### Reading stdin in `opa exec`

The `opa exec` command now supports reading `input` documents from
stdin with the `--stdin-input` (`-I`) flag.

v0.65.0
This release contains a mix of features and bugfixes.

Log message:
Revbump all Go packages after go122 security update

Log message:
Revbump all Go packages after go122 update