-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update everything (major) #56
Draft
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-everything
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Here's the code health analysis summary for commits Analysis Summary
|
26d9973
to
eba6173
Compare
8e5a0d6
to
ef0be35
Compare
ef0be35
to
a3cc02b
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
70b292a
to
3089d32
Compare
3089d32
to
65c2885
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3
->v4
v4
->v5
v0.68.0
->v1.2.0
v3
->v6
v1
->v2
v5
->v6
Release Notes
GoogleCloudPlatform/release-please-action (GoogleCloudPlatform/release-please-action)
v4
Compare Source
actions/setup-go (actions/setup-go)
v5
Compare Source
open-policy-agent/opa (github.com/open-policy-agent/opa)
v1.2.0
Compare Source
This release contains a mix of features, performance improvements, and bugfixes.
Parameterized Rego Tests (#2176)
Rego tests now support parameterization, allowing a single test rule to include multiple, hierarchical, named test cases.
This feature is useful for data-driven testing, where a single test rule can be used for multiple test cases with different inputs and expected outputs.
See the documentation for more information.
Authored by @johanfylling, reported by @anderseknert
Performance Improvements
opa fmt
3x faster formatting (#7341) authored by @anderseknertTopdown and Rego
Runtime, Tooling, SDK
BuildAnnotationSet
toast
v0 (#7347) authored by @anderseknert[]byte
(#7379) authored by @dennygursky--v0-compatible
isn't respected for custom bundles (#7338) authored by @johanfyllingopa test --bench
(#7205) authored by @anderseknertopa exec
output (#7373) authored by @anderseknertDocs, Website, Ecosystem
v1 import
(#7391) authored by @charlieegan3--v1-compatible
mentions outside the v1 upgrade guide and v0 compatibility docs (#7337) authored by @johanfyllingMiscellaneous
make test-short
task (#7364) (authored by @anderseknert)TestIntraQueryCache_ClientError
andTestInterQueryCache_ClientError
(#7280) authored by @Juneezeev1.1.0
Compare Source
This release contains a mix of features, performance improvements, and bugfixes.
Performance Improvements
opa bench
(#7291) authored by @anderseknertio.jwt
token verification built-ins (#7274) authored by @johanfyllingTopdown and Rego
numbers.range
built-in (#7269) authored by @anderseknertRuntime, Tooling, SDK
opa repl
(#7301) authored by @anderseknert reported by @tsandall--v0-compatible
foropa eval
partial eval support modules (#7251) authored by @johanfyllinglinter-settings
configuration name (#7244) authored by @JuneezeeDocs, Website, Ecosystem
Miscellaneous
v1.0.1
Compare Source
This is a bug fix release addressing the following issues:
Addressing
CVE-2024-45341
andCVE-2024-45336
vulnerabilities in the Go runtime.Fixing an issue where the rego-version for individual modules was lost during bundle deactivation (bundle lifecycle) if this version diverged from the active runtime rego-version.
This could cause reloading of v0 bundles to fail when OPA was not running with the
--v0-compatible
flag.v1.0.0
Compare Source
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:
if
for all rule definitions andcontains
for multi-value rules is now mandatory, not just when using therego.v1
import.every
,in
) are available without any imports.opa check --strict
) are now the default. Duplicate imports and imports which shadow each other are no longer allowed.if you must continue to support v0 Rego.
Read more about the OPA 1.0 announcement here on our blog.
Following are other changes that are included in OPA 1.0.
Improvements to memory allocations
PRs #7172, #7190, #7193, #7165, #7168, #7191 & #7222 together improve the memory performance of OPA. Key strategies
include reusing pointers and optimizing array and object operations, minimizing intermediate object creation, and using
sync.Pool
to manage memory-heavy operations. These changes cumulatively greatly reduced the number of allocations and improved
evaluation speed by 10-20%. Additional benchmarks highlighted significant memory and speed improvements in custom
function evaluation.
Authored by @anderseknert.
Wrap http.RoundTripper for SDK users
PR #7180 adds an
EvalHTTPRoundTrip
EvalOption and query-levelWithHTTPRoundTrip
option.Both use a new function type which converts an
http.Transport
configured by topdown to anhttp.RoundTripper
.This supports use cases requiring the customization of the
http.send
built in behavior.Authored by @evankanderson.
Improvements to scientific notation parsing in
units.parse
PR #7147 extends the behaviour of
extractNumAndUnit
to supportscientific notation values. This means values such as
1e3KB
can now be handled by this function.Authored by @berdanA.
Support customized buckets
bundle_loading_duration_ns
metricPR #7156 extends OPA’s Prometheus configuration to allow the
setting of user defined buckets for metrics. This aids when debugging the loading of slow bundles.
Authored by @jwu730-1.
Test suite performance improvements
PR #7126 updates tests to improve performance. Topdown and
storage/disk/
tests now run around 50% and 75% faster respectively.
Authored by @philipaconrad.
OPA 1.0 Preparation
rego.v1
andfuture.keywords
imports for v1 by @johanfylling in #7224--rego-v1
cmd flag to--v0-v1
by @johanfylling in #7225Topdown and Rego
topdown/cache
by @evankanderson in #7188to_number
now rejects "Inf", "Infinity" and "NaN" values by @sikehish in #7203Runtime, Tooling, SDK
opa build
: provide an option to preserve print statements for the "wasm" target (#7194) by @me-viper in #7195opa eval
: Return error if illegal arguments passed with--unknowns
flag by @kd-labs in #7149Docs, Website, Ecosystem
Dependency Updates
v0.70.0
Compare Source
This release contains a mix of features, performance improvements, and bugfixes.
Optimized read mode for OPA's in-memory store (#7125)
A new optimized read mode has been added to the default in-memory store, where data written to the store is eagerly converted
to AST values (the data format used during evaluation). This removes the time spent converting raw data values to AST
during policy evaluation, thereby improving performance.
The memory footprint of the store will increase, as processed AST values generally take up more space in memory than the
corresponding raw data values, but overall memory usage of OPA might remain more stable over time, as pre-converted data
is shared across evaluations and isn't recomputed for each evaluation, which can cause spikes in memory usage.
This mode can be enabled for
opa run
,opa eval
, andopa bench
by setting the--optimize-store-for-read-speed
flag.More information about this feature can be found here.
Co-authored by @johanfylling and @ashutosh-narkar.
Topdown and Rego
json.match_schema
built-in function (#7011) authored by @anderseknert reported by @lcarvaopa check
where a file that referenced non-provided schemas failed validation (#7124) authored by @tjonsyes
/no
values as boolean. The usage of yaml.v2 in the parser was unintentional and now has been updated to yaml.v3 (#7090) authored by @anderseknertRuntime, Tooling, SDK
opa check
respect--ignore
when--bundle
flag is set (#7136) authored by @anderseknertsuperfluous call to WriteHeader()
while still returning200
HTTP status code. Now, errors encoding the payload properly lead to500
HTTP status code, without extra logs. Also use Header().Set() not Header().Add() to avoid duplicate content-type headers (#7114) authored by @srenatusfile://
format for TLS key material file flags inopa run
(#7094) authored by @alexrohozneanuDocs, Website, Ecosystem
Miscellaneous
v0.69.0
Compare Source
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 (#6908)
OPA now has a new inter-query value cache added to the SDK. It is intended to be used for values that are expensive to compute and can be reused across multiple queries. The cache can be leveraged by built-in functions to store values that otherwise aren't appropriate for the existing inter-query cache; for instance when the entry size isn't an appropriate or primary limiting factor for cache eviction.
The default size of the inter-query value cache is unbounded, but can be configured via the
caching.inter_query_builtin_value_cache.max_num_entries
configuration field. OPA will drop random items from the cache if this limit is exceeded.The cache is used by the
regex
andglob
built-in functions, which previously had individual, non-configurable caches with a max entry size of100
each.Currently, the cache is only exercised when running OPA in server mode (ie.
opa run -s
). Also this feature is unsupported for WASM.Authored by @ashutosh-narkar, reported by @amirsalarsafaei
Topdown and Rego
ast
,topdown
,rego
etc. packages to be1.0
compatible (authored by @johanfylling)Module.String()
includeif
/contains
for v1 modules (#6973) authored by @johanfylling reported by @nikpivkinhttp.send
latency timer when an error is encountered (#7007) authored by @lukyerwith
's target (#6979) authored by @srenatus reported by @bluebrownRuntime, Tooling, SDK
sdk
,downlaod
,server
,cmd
etc. packages to be1.0
compatible (authored by @johanfylling)--v0-compatible
flag to make OPA behave asv0.x
postv1.0
release (#7065) authored by @johanfyllingRegoOption
launch option to debugger for setting custom Rego options (#7045) authored by @johanfyllingInput
andData
variable scopes to ease discoverability of the scopes (#7074) authored by @johanfyllingDocs, Website, Ecosystem
1.0
compatible (#7033) authored by @charlieegan3Miscellaneous
golangci/golangci-lint-action (golangci/golangci-lint-action)
v6
Compare Source
v5
Compare Source
v4
Compare Source
google-github-actions/auth (google-github-actions/auth)
v2
Compare Source
Floating v2 alias
wagoid/commitlint-github-action (wagoid/commitlint-github-action)
v6
Compare Source
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.