Bumps [github.com/open-policy-agent/opa](https://github.com/open-policy-agent/opa) from 1.18.1 to 1.19.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/open-policy-agent/opa/releases">github.com/open-policy-agent/opa's releases</a>.</em></p> <blockquote> <h2>v1.19.0</h2> <p>This release contains a mix of new features and bug fixes. Notably:</p> <ul> <li>A fixed SQL injection vector in the Compile API</li> <li>Stricter safety checking for Rego assignments (<code>:=</code>)</li> <li>A cgo-free, faster WebAssembly runtime (wazero replaces wasmtime-go)</li> <li>Startup warnings for unknown configuration options</li> <li>A new <code>strings.split_n</code> built-in function</li> <li>A REPL line reader that handles pasted input correctly, migrating existing history files</li> </ul> <h3>Fix SQL injection vector in Compile API: Quote SQL filter field identifiers (<a href="https://redirect.github.com/open-policy-agent/opa/pull/8945">#8945</a>)</h3> <p>The field names in the SQL emitted by the Compile API come from partially evaluated refs, so a policy that selects a dynamic key — such as <code>input.fruits[input.column]</code> — puts caller-controlled text in an identifier position. That text was emitted verbatim, which turns</p> <pre lang="sql"><code>WHERE fruit.name = 'allowed' </code></pre> <p>into</p> <pre lang="sql"><code>WHERE fruit.name = 'allowed' OR 1=1 -- = 'allowed' </code></pre> <p>and an application appending the filter to its query returns rows the policy denies.</p> <p>Field segments that are not bare identifiers are now quoted at the UCAST-to-SQL boundary, with any embedded quote character escaped. Ordinary column names stay unquoted, so existing filters keep their current shape and remain case-insensitive on Postgres.</p> <p>Authored by <a href="https://github.com/thevilledev"><code>@thevilledev</code></a></p> <h3>Behavior change: stricter safety for assignment (<code>:=</code>) (<a href="https://redirect.github.com/open-policy-agent/opa/issues/3546">#3546</a>)</h3> <p>The assignment operator (<code>:=</code>) is documented as "syntactic sugar for <code>=</code>, local variable creation, and additional compiler checks," and the safety checker reflects that: after rewriting, <code>:=</code> is treated identically to <code>=</code> (unification), so an assignment's right-hand side can be made safe by unifying "backwards" through the left-hand side. This means policies like <code>x := y; x = 7</code> compile (binding <code>y</code> to <code>7</code>) even though <code>y</code> is never assigned, and <code>x := y; obj[x]</code> can silently degrade an expected constant-time lookup into full iteration.</p> <p>This change makes the right-hand-side of <code>:=</code> be treated as a read that must be made safe by other expressions, and can no longer be satisfied through the left-hand-side. Affected policies that previously compiled now fail with a <code>rego_unsafe_var_error</code>. Reference iteration on the right-hand-side (e.g. <code>some k; v := obj[k]</code>) is unaffected.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/open-policy-agent/opa/blob/main/CHANGELOG.md">github.com/open-policy-agent/opa's changelog</a>.</em></p> <blockquote> <h2>1.19.0</h2> <p>This release contains a mix of new features and bug fixes. Notably:</p> <ul> <li>A fixed SQL injection vector in the Compile API</li> <li>Stricter safety checking for Rego assignments (<code>:=</code>)</li> <li>A cgo-free, faster WebAssembly runtime (wazero replaces wasmtime-go)</li> <li>Startup warnings for unknown configuration options</li> <li>A new <code>strings.split_n</code> built-in function</li> <li>A REPL line reader that handles pasted input correctly, migrating existing history files</li> </ul> <h3>Fix SQL injection vector in Compile API: Quote SQL filter field identifiers (<a href="https://redirect.github.com/open-policy-agent/opa/pull/8945">#8945</a>)</h3> <p>The field names in the SQL emitted by the Compile API come from partially evaluated refs, so a policy that selects a dynamic key — such as <code>input.fruits[input.column]</code> — puts caller-controlled text in an identifier position. That text was emitted verbatim, which turns</p> <pre lang="sql"><code>WHERE fruit.name = 'allowed' </code></pre> <p>into</p> <pre lang="sql"><code>WHERE fruit.name = 'allowed' OR 1=1 -- = 'allowed' </code></pre> <p>and an application appending the filter to its query returns rows the policy denies.</p> <p>Field segments that are not bare identifiers are now quoted at the UCAST-to-SQL boundary, with any embedded quote character escaped. Ordinary column names stay unquoted, so existing filters keep their current shape and remain case-insensitive on Postgres.</p> <p>Authored by <a href="https://github.com/thevilledev"><code>@thevilledev</code></a></p> <h3>Behavior change: stricter safety for assignment (<code>:=</code>) (<a href="https://redirect.github.com/open-policy-agent/opa/issues/3546">#3546</a>)</h3> <p>The assignment operator (<code>:=</code>) is documented as "syntactic sugar for <code>=</code>, local variable creation, and additional compiler checks," and the safety checker reflects that: after rewriting, <code>:=</code> is treated identically to <code>=</code> (unification), so an assignment's right-hand side can be made safe by unifying "backwards" through the left-hand side. This means policies like <code>x := y; x = 7</code> compile (binding <code>y</code> to <code>7</code>) even though <code>y</code> is never assigned, and <code>x := y; obj[x]</code> can silently degrade an expected constant-time lookup into full iteration.</p> <p>This change makes the right-hand-side of <code>:=</code> be treated as a read that must be made safe by other expressions, and can no longer be satisfied through the left-hand-side. Affected policies that previously compiled now fail with a <code>rego_unsafe_var_error</code>. Reference iteration on the right-hand-side (e.g. <code>some k; v := obj[k]</code>) is unaffected.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/open-policy-agent/opa/commit/1e32c796e8979b1bda2f768138500b1deb95ff24"><code>1e32c79</code></a> Prepare v1.19.0 release (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8955">#8955</a>)</li> <li><a href="https://github.com/open-policy-agent/opa/commit/db035b09fc8b4b7f1b37558c4fde033209e17cc8"><code>db035b0</code></a> Add support for Go 1.27 & jsonv2 (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8947">#8947</a>)</li> <li><a href="https://github.com/open-policy-agent/opa/commit/27fe5ceac871d020e10dd4a92d4eb6fa7070400a"><code>27fe5ce</code></a> ast: Fix leaky <code>future.keywords.not</code> import in Rego v0 (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8953">#8953</a>)</li> <li><a href="https://github.com/open-policy-agent/opa/commit/ab2187089a8dea0d7f1ea611fe8f62db874498b7"><code>ab21870</code></a> format: Keep rule body inline when the head spans multiple lines (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8904">#8904</a>)</li> <li><a href="https://github.com/open-policy-agent/opa/commit/95090fa4eb7a8afe2d7a08742086be0344e9e065"><code>95090fa</code></a> Add strings.split_n built-in function (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8915">#8915</a>)</li> <li><a href="https://github.com/open-policy-agent/opa/commit/12a86ed2a70384eb24754d7be115c90f98736011"><code>12a86ed</code></a> build(deps): bump find-my-way and prisma in /e2e/api/compile/prisma</li> <li><a href="https://github.com/open-policy-agent/opa/commit/18815e2b02711650be1c55148e67de5b4e614a6f"><code>18815e2</code></a> build(deps): bump the dependencies group across 2 directories with 5 updates</li> <li><a href="https://github.com/open-policy-agent/opa/commit/f1e2ac07e4ad18be65495451ba648a85af0e583b"><code>f1e2ac0</code></a> build(deps): bump postcss from 8.5.15 to 8.5.23 in /docs</li> <li><a href="https://github.com/open-policy-agent/opa/commit/d9c7856eaea45ed0ee8c3709d8ef0151b17ba43c"><code>d9c7856</code></a> build(deps): bump js-yaml from 5.2.1 to 5.2.2 in /docs</li> <li><a href="https://github.com/open-policy-agent/opa/commit/69d2cc04a0de02892e4bad95cc416b9baa9a0b3b"><code>69d2cc0</code></a> tester: make Result JSON round-trippable (<a href="https://redirect.github.com/open-policy-agent/opa/issues/8946">#8946</a>)</li> <li>Additional commits viewable in <a href="https://github.com/open-policy-agent/opa/compare/v1.18.1...v1.19.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Coder is a self-hosted platform for cloud development environments and AI coding agents. Workspaces are defined with Terraform, connected through a secure Wireguard® tunnel, and automatically shut down when not used. Coder Agents runs a native AI coding agent whose loop executes in the control plane on your infrastructure, with no API keys in workspaces.
- Define cloud development environments in Terraform
- EC2 VMs, Kubernetes Pods, Docker Containers, etc.
- Automatically shutdown idle resources to save on costs
- Onboard developers in seconds instead of days
- Delegate coding work to AI agents on your infrastructure
- Bring any model (Anthropic, OpenAI, Google, Bedrock, self-hosted)
- No LLM credentials in workspaces, user identity on every action
- Centralized model governance, cost tracking, and audit logging
Quickstart
The most convenient way to try Coder is to install it on your local machine and experiment with provisioning cloud development environments using Docker (works on Linux, macOS, and Windows).
# First, install Coder
curl -L https://coder.com/install.sh | sh
# Start the Coder server (caches data in ~/.cache/coder)
coder server
# Navigate to http://localhost:3000 to create your initial user,
# create a Docker template and provision a workspace
Install
The easiest way to install Coder is to use the
install script for Linux
and macOS. For Windows, use the latest ..._installer.exe file from GitHub
Releases.
curl -L https://coder.com/install.sh | sh
You can run the install script with --dry-run to see the commands that will be used to install without executing them. Run the install script with --help for additional flags.
See install for additional methods.
Once installed, you can start a production deployment with a single command:
# Automatically sets up an external access URL on *.try.coder.app
coder server
# Requires a PostgreSQL instance (version 13 or higher) and external access URL
coder server --postgres-url <url> --access-url <url>
Use coder --help to get a list of flags and environment variables. See the install guides for a complete tutorial.
Documentation
Browse the documentation or visit a specific section below:
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Coder Agents: Delegate coding work to AI agents running on your self-hosted infrastructure
- Administration: Learn how to operate Coder
- Premium: Learn about paid features built for large teams
- IDEs: Connect your existing editor to a workspace
Support
Feel free to open an issue if you have questions, run into bugs, or have a feature request.
Join our Discord to provide feedback on in-progress features and chat with the community using Coder!
Integrations
New integrations are always in progress. Open an issue to request one. Contributions are welcome in any official or community repository.
Official
- Coder Registry: Templates, modules, and integrations for common development environments
- VS Code Extension: Open any Coder workspace in VS Code with a single click
- JetBrains Toolbox Plugin: Open any Coder workspace from JetBrains Toolbox with a single click
- JetBrains Gateway Plugin: Open any Coder workspace in JetBrains Gateway with a single click
- Dev Containers: Build development environments using
devcontainer.jsonon Docker, Kubernetes, and OpenShift - Kubernetes Log Stream: Stream Kubernetes Pod events to the Coder startup logs
- Self-Hosted VS Code Extension Marketplace: A private extension marketplace that works in restricted or airgapped networks integrating with code-server.
- GitHub Actions: An action to set up the Coder CLI in GitHub workflows
Community
- Community Templates: Community-contributed workspace templates in the Coder Registry
- Community Modules: Community-contributed modules to extend Coder templates
- Provision Coder with Terraform: Provision Coder on Google GKE, Azure AKS, AWS EKS, DigitalOcean DOKS, IBMCloud K8s, OVHCloud K8s, and Scaleway K8s Kapsule with Terraform
- Coder Template GitHub Action: A GitHub Action that updates Coder templates
- Discord: Chat with the community and provide feedback on in-progress features
Contributing
New contributors are always welcome. If you are new to the Coder codebase, see the contribution guide to get started.
Hiring
Apply on the careers page if you are interested in joining the team.
