Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/open-policy-agent/conftest v0.63.0v0.66.0 age adoption passing confidence
github.com/open-policy-agent/opa v1.12.3v1.13.1 age adoption passing confidence
github.com/styrainc/regal v0.29.2v0.38.1 age adoption passing confidence

Release Notes

open-policy-agent/conftest (github.com/open-policy-agent/conftest)

v0.66.0

Compare Source

Changelog

OPA Changes
Other Changes

v0.65.0

Compare Source

Changelog

New Features
Bug Fixes
OPA Changes
Other Changes

v0.64.0

Compare Source

Changelog

New Features
Bug Fixes
OPA Changes
Other Changes
open-policy-agent/opa (github.com/open-policy-agent/opa)

v1.13.1

Compare Source

v1.13.0

Compare Source

This release contains a mix of new features, performance improvements, and bugfixes. Notably:

  • A new immediate upload trigger mode in the Decision Logger
  • A new array.flatten built-in function
  • Numerous performance improvements
Immediate Upload Trigger Mode in Decision Logger (#​8110)

An immediate trigger mode has been added to the Decision Logger; enabled by setting the decision_logs.reporting.trigger configuration option to immediate.
When enabled, log events are pushed to the log service as soon as the configured upload chunk size criteria is met; or, at latest, when the configured upload delay is reached.

Authored by @​sspaink

Runtime, SDK, Tooling
Compiler, Topdown and Rego
Performance
Docs, Website, Ecosystem
Miscellaneous
  • Decoupled the Rego job check from the Go job checks in the Github PR workflow (#​8203) authored by @​SeanLedford
  • build: Format pr_check.rego with opa fmt (#​8201) authored by @​thevilledev
  • build: Migrate PR check to OPA policy (#​8183) authored by @​SeanLedford
  • build: Run go get against main to spot redacted (#​8146) authored by @​charlieegan3
  • deps: Switch to maintained go.yaml.in/yaml/v3 yaml library (#​8182) authored by @​mrueg
  • test/cases: Increase yaml test coverage for some regex and string builtins (#​8152) authored by @​srenatus
  • Dependency updates; notably:
    • build: bump golang from 1.25.5 to 1.25.6 (#​8224) authored by @​srenatus
    • build(deps): bump go.opentelemetry.io deps from 1.38.0/0.63.0 to 1.39.0/0.64.0
    • build(deps): bump klauspost/compress from v1.18.1 to v1.18.2 (#​8184) authored by @​srenatus
      because of redaction warning
    • build(deps): bump github.com/go-ini/ini from v1.67.0 to gopkg.in/ini.v1 v1.67.1 (#​8208) authored by @​gabrpt
styrainc/regal (github.com/styrainc/regal)

v0.38.1

Compare Source

This patch release fixes several bugs including some found in the recent v0.38.0 release, as well some other improvements.

Bug Fixes

Improvements

  • Code action for prefer-equals-comparison fixer now available in the language server (#​1810)
  • New option for prefer-value-in-head rule to count interpolated strings as scalars (#​1817)
  • Minor performance improvement for any_set_item, used for selecting items from sets (#​1815)

Changelog

v0.38.0

Compare Source

Happy New Year from the Regal maintainers!

Feature: String Interpolation Support

v0.38.0 of your favorite Rego linter, debugger and language server brings full support for OPA's new string interpolation feature. This means not only that Regal lints code found inside interpolated strings, but that you'll have access to all your favorite language server features within them too — like code completions, tooltips on hover, or document highlighting. You can even use the debugger to step through interpolated expressions! If you haven't yet tried it out, grab OPA v1.12.2, Regal v0.38.0 and enjoy an absolutely awesome addition to the Rego language!

In addition to this, we have a number of fun new features and performance improvements.

New Rule: disallow-rego-v1

Category: custom

This optional new rule flags the use of import rego.v1 in Rego policies (#​1778). Since OPA v1.0 (December 2024), this import is a no-op and no longer needed. The rule helps users maintain clean code by preventing this outdated import from appearing in new policies. Teams standardizing on OPA 1.0+ can enable this rule to enforce modern Rego standards.

package example

import rego.v1 # <-- Happy 2026! Time to stop doing this!

Authored by @​SeanLedford.

New Fixers

@​SeanLedford has also done some great work to help expand Regal's auto-fixing capabilities by having regal fixers added for three more rules.

See (#​1790) and (#​1794) for more details.

Performance

The fixer saw a 12% performance improvement by reusing the linter, reducing allocations from 2.3M to 2.0M operations (#​1783). Additional optimizations include:

  • faster file filtering by avoiding recompiled ignore patterns (#​1758),
  • better built-in function handling by registering Regal's functions globally only once (#​1788),
  • and more efficient AST location serialization (#​1758)

To track ongoing performance work, a new post-merge benchmark-recording workflow was added (#​1793).

LSP: New Ignore Code Action

The language server now supports a code action to quickly add regal ignore configuration for specific rules directly from the editor (#​1777).

Changelog

v0.37.0

Compare Source

Regal v0.37.0

This release features a new linter rule, several new language server features, and many improvements and fixes. The two major OPA versions bumped since the last release additionally contains several performance improvements that were contributed as part of developing Regal!

New Rule: prefer-equals-comparison

The prefer-equals-comparison linter rule recommends using the == operator for equality comparison over the unification operator =. The rule helps improve code clarity by using operators for their intended purposes: := for assignment, == for equality comparison, and = for unification. The linter identifies when = is used for comparison by checking if both sides of the operator are "unassignable".

Avoid

input.request.method = "GET"

Prefer

input.request.method == "GET"

There are some certainly valid use cases for the unification operator! But simple equality comparison is not one. For more information, see the documentation for the rule. As an amusing aside, this fixes one of the first issues created in the project!

Language server: Document highlighting to help show where function args are referenced

Document highlighting is one of the more subtle features of the LSP specification, but a really helpful one when implemented well. The experimental first implementation that shipped with Regal v0.36.0 is no longer experimental, and has also been extended to highlight usage of function argument variables inside of a function head or body.

documenthighlighting

Language server: Selection ranges

Selection ranges provide smart selection of code that can expand and shrink based on knowledge of the code rather than simple text properties, like hyphens or whitespace. This makes moving code around extremely fast, and without leaving the keyboard. Consult the language server docs for how to enable this in your editor

selectionranges

Improvements

  • The pointless-reassignment rule would previously only flag reassignment at the top level of a rule body. Now it flags pointless reassignments also in nested bodies, like comprehensions, every statements, and so on.

Windows compatibility improvements

In this release we have fixed various Windows bugs (Language Server Init, Goto Definition, Error Popups) in #​1740, #​1737, #​1736, following #​1633, and #​1642 last release. Reported and verified by geirs73.

These fixes have also made it possible to run our test suites on Windows runners to catch issues sooner in future. A huge thanks to @​charlieegan3 for his tireless work on this!

Bugs fixed

Dependency Updates:

Go modules:

  • github.com/open-policy-agent/opa: v1.8.0v1.10.1
  • github.com/arl/statsviz: v0.7.1v0.7.2
  • github.com/go-git/go-git/v5: v5.16.2v5.16.3
  • github.com/olekukonko/tablewriter: v0.0.5v1.1.0
  • github.com/spf13/cobra: v1.9.1v1.10.1
  • github.com/spf13/pflag: v1.0.7v1.0.10
  • Removed: github.com/coreos/go-semver: v0.3.1

GitHub Actions:

  • open-policy-agent/setup-opa: v2.2.0v2.3.0
  • actions/cache: v4.2.4v4.3.0
  • actions/upload-artifact: v4.6.2v5.0.0
  • golangci/golangci-lint-action: v2.4.0v2.5.0
  • actions/setup-go: v5.5.0v6.0.0

Support

If you encounter any issues with this release, please either file an issue, or let us know in the #opa-regal channel in the OPA Slack!

Changelog


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jan 19, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -t ./...
go: github.com/styrainc/regal@v0.38.1: parsing go.mod:
	module declares its path as: github.com/open-policy-agent/regal
	        but was required as: github.com/styrainc/regal

@renovate renovate bot force-pushed the renovate/main-go-modules branch from a167a6d to c49a110 Compare January 29, 2026 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants