InfracodebaseInfracodebase

Product updates

New features, improvements, and fixes we’ve shipped to Infracodebase.

Releases over time

217 releases

Showing 25 releases from the last month.

v2.31.0
Latest

Added

  • A new System theme option automatically matches your operating system's light or dark setting, and is now the default for new visitors.
  • The theme picker in Appearance Settings shows three options, Light, Dark, and System, each with a preview swatch.
  • The command palette now lists all three theme options and shows which one is currently active.

Improved

  • The theme toggle in the editor now cycles through Light, Dark, and System.
  • Sign-in and sign-up pages now match your selected theme instead of always appearing in dark mode.
  • Native browser controls (scrollbars, form inputs, date pickers) now match the active theme.
v2.30.1

Fixed

  • Shared links to blog posts, pricing, docs, and other public pages now unfurl with the correct title, description, and preview image instead of always showing the homepage content.
  • Blog post link previews now include a dedicated card with the post's own title and excerpt.
  • The app icon now displays with rounded corners in link previews and browser tabs.
v2.30.0

Added

  • New public API endpoints list all version control connections for an enterprise, and the repositories visible to each, across every provider (GitHub, GitLab, and more).
  • Workspace creation and repository linking in the public API now accept a provider-neutral connection and path selector instead of GitHub-specific fields, adding support for GitLab and future providers.
  • Repository link responses now include a warning when a repo connects successfully but webhook registration fails, so push-driven compliance gaps are visible instead of silent.

Improved

  • Breaking change: the GitHub-only installations endpoints have been removed from the public API. Use the new version control connections endpoints instead.
  • Breaking change: workspace creation and repository linking in the public API no longer accept GitHub-specific fields (installation_id, owner, repo). Use the new connection_id and path fields instead.
v2.29.0

Added

  • Compliance evaluations now show the exact ruleset version each rule was checked against, on the findings table, ruleset score chips, rule workpapers, and the compliance dashboard filter.
  • Partial re-runs now show both the freshly evaluated version and a note for any rules carried over from an earlier run, so results are never silently mixed together.
  • Ruleset pages now show the current version number and its publish date, with the activity feed grouped by the version each change produced.
  • The public API's ruleset responses now include a version field.
v2.28.0

Added

  • GitLab can now be connected as a version control provider using a personal or group access token, including support for self-managed GitLab instances.
  • A new Version Control settings page lists all connected providers, GitHub and GitLab, in one place, with a detail page for each.
  • The repository picker and import flow now show repositories from all connected providers together, instead of just GitHub.
  • Compliance CI checks (status checks on pull and merge requests, and the default branch) now work for GitLab-linked workspaces, in addition to GitHub.
  • Provider icons now appear throughout the app wherever a linked repository is shown.

Improved

  • Compliance CI, git sync, and repository links now work the same way across every connected provider, not just GitHub.
  • Repository links throughout the app now resolve to the correct host for self-managed GitLab or GitHub Enterprise Server instances.
  • The old GitHub settings page now redirects automatically to the new Version Control settings page.
v2.27.1

Fixed

  • Deleting an enterprise with an active subscription now cancels it first; if billing is temporarily unreachable, the deletion is safely aborted so it can be retried without losing billing information.
  • Canceling a subscription that is already canceled no longer permanently blocks enterprise deletion.
v2.27.0

Added

  • Rulesets now keep a full version history, so you can always see exactly which rules and policies were in effect for a given approval or edit.
  • Compliance evaluations record the exact rule version they were checked against, so historical results always resolve to the rules that actually ran, even after they are edited or deleted later.
  • The policy panel now flags when a check is out of date with its rule text, and clears the flag automatically once the check is updated.

Improved

  • Deleting a ruleset or rule now hides it immediately everywhere while keeping historical findings and evidence intact.
  • Approved exceptions (suppressions) now survive policy rewrites without needing to be re-approved.
  • Workpapers now show a clear message when a historical finding's check is no longer available, instead of an error or blank space.

Fixed

  • Fixed an error that could block deleting an enterprise, workspace, or user account that owned a versioned ruleset.
v2.26.0

Added

  • Compliance evaluations can now be scoped to a single ruleset, rule, or batch of rules, re-evaluating only what you specify while carrying forward prior results for everything else.
  • Triggering an evaluation against a specific branch, tag, or commit now evaluates that exact commit, rather than always using the current checkout.
  • Evaluation and workspace API responses now include more context: a direct link to the results page, whether each rule is enabled or disabled, and a way to resolve workspace context directly from a repository URL.

Improved

  • Evaluation and workspace APIs now correctly scope results to the requested branch, ruleset, or workspace type, fixing several cases where they mixed in unrelated data.

Fixed

  • Fixed several issues where triggering or checking a compliance evaluation could return a stale or incorrect evaluation (from before the trigger, for the wrong ruleset or rule, or for an outdated commit) instead of the current one.
  • Fixed a bug where evaluation results could be incorrectly reused after the active rules in the ruleset had changed.
  • Workspaces can no longer be attached to a ruleset that has been disabled at the enterprise level, closing a way to bypass governance.
v2.25.1

Fixed

  • The workspace creation wizard now reliably delivers your opening prompt to the editor, even if the page reloads mid-send or a deployment happens while you are creating the workspace.
  • If a deployment causes workspace creation to fail, the wizard now automatically reloads and clearly explains that no workspace was created and the prompt needs to be re-entered, instead of failing silently or locking the Create button.
v2.25.0

Added

  • Reviewers can now see which policy checks approving a rule deletion would stop enforcing, shown directly on the deletion card.
  • The AI agent can now request a policy check for a rule without also rewriting the wording of the rule, avoiding unnecessary cosmetic edits.
  • The pending-review queue now lists all proposals, new rulesets and edits alike, in a single list sorted newest first.
  • A stalled policy-authoring draft now shows a clear "Authoring stalled" indicator instead of silently disappearing, so it is obvious that approving would leave the rule without a working check.

Improved

  • Policy diffs on review cards now use a clearer line-by-line view with add/remove markers and highlighted word-level edits.
  • The Approve All button is now disabled, with an explanation, while a policy check is still being authored, preventing approval of a check you have not seen yet.
  • Submitting changes that conflict with an already-pending review now shows a clear error naming the specific rules in conflict, instead of a generic error.

Fixed

  • Fixed a security vulnerability in HTML sanitization (DOMPurify) that could allow cross-site scripting.
  • Proposing a policy check, or a wording change, for a rule no longer accidentally reverts another pending change already staged for the same rule.
v2.24.1

Fixed

  • Spam-clicking or double-clicking Create Workspace no longer creates duplicate workspaces; the button now locks immediately and shows a spinner while the workspace is created.
  • If the workspace creation prompt cannot be saved in your browser (for example, private browsing mode or a storage limit), the workspace is now still created and opened normally instead of showing a misleading error.
v2.24.0

Added

  • When the AI auditor and a policy check disagree on a compliance rule, a new "Why they disagree" section explains which signal was wrong and why.
  • You can now propose a verified policy fix, or a rule wording change, directly from the conflict diagnosis panel, entering the normal review queue for approval.
  • Dismissed conflicts remain visible with attribution, and can be reopened later if worth revisiting.
  • When a finding is confirmed as a real violation, the panel now offers a pre-drafted, editable justification for requesting a compliance exception.

Fixed

  • Error messages in the exception dialog now correctly distinguish network failures from server errors and advise you accordingly.
  • Reviewing a proposed rule change no longer removes a working policy check just because the rule was flagged as having no automatable check.
v2.23.0

Added

  • The compliance rule result page now has a table of contents that highlights the active section as you scroll.
  • Exception and challenge actions (grant exception, request exception, correct verdict, challenge finding, revoke exception, re-run rule) are now available directly on the rule result page.
  • The rule result page now includes a History section merging machine runs and human decisions into one chronological timeline, so a revoked waiver stays visible.
  • While a rule is being re-evaluated, the page shows the last result and updates automatically once the new verdict lands, instead of a blank spinner.

Improved

  • The rule result page is now a narrative read (requirement, finding, what changed, how it was checked, history) instead of a workpaper beside a history rail, with policy check results explained in plain language.
  • Timestamps on the rule result page are now pinned to UTC, so shared links read the same for every viewer.
  • Enterprise-level compliance approvers can now see and use all actions on the rule result page.

Fixed

  • Fixed a finding showing different verdict labels in different places (badge, timeline, dashboard) for the same result, and fixed a standing exception that was later revoked no longer disappearing from the history record.
v2.22.0

Added

  • Compliance findings now show a Verified, Needs review, or Judgment only badge indicating whether a deterministic policy check corroborates what the AI decided.
  • Each compliance finding now has its own shareable result page with the full workpaper and a run history showing how the rule has scored over time.
  • Deterministic policy checks are now drafted automatically when a rule is created or edited, and reviewers can edit, add, or remove them during review and approval.
  • Rule cards now show a Policy as code or Judgment only chip indicating whether a machine check exists for the rule.

Improved

  • The compliance findings list is now a flat, sortable table with failures first, replacing the grouped accordion view, and ruleset chips above it can be clicked to filter the table.
  • Draft policy authoring now retries automatically on failure, so a transient error no longer permanently leaves a rule without a machine check.

Fixed

  • Fixed hand-written policies on staged rules being silently dropped instead of applied on approval.
  • Fixed a policy edit on the rule detail page being applied live instead of going through review.
v2.21.0

Added

  • Claude Sonnet 5, Claude Opus 5, and Claude Fable 5 are now available as model choices.

Improved

  • Default models for coding, architecture, ruleset, and image-extraction features have been upgraded to Claude Sonnet 5 and Opus 5.
  • Claude Opus 4.8, 4.7, 4.6, and Sonnet 4.6 now support the full 1 million token context window at standard rates, with no price premium above 200k tokens.

Fixed

  • Claude Opus 4.1 and Claude Haiku 3.5 are now marked deprecated and hidden from the model selector.
v2.19.0

Added

  • Added a Disconnect all button to remove every connected GitHub org and personal account at once, with a confirmation summary of affected workspaces.
  • Added per-account Connect and Disconnect controls on the GitHub settings page.
  • The GitHub settings page now shows a warning banner and the last known state when GitHub cannot be reached, and updates automatically when installations change.

Improved

  • The GitHub App and personal account connections are now shown separately, and installation status stays consistent across settings pages, including through account renames and app reinstalls.
  • Connecting and disconnecting GitHub accounts now requires the Manage Integrations permission.

Fixed

  • Fixed disconnecting an account leaving the GitHub App installation and CI compliance checks active.
  • Fixed reinstalled or renamed GitHub accounts appearing as duplicate or missing entries.
  • Fixed CI compliance checks running against repositories that had already been disconnected from an enterprise.
v2.18.0

Added

  • Module catalog and workspace cards now show a Terraform registry badge for modules published to your connected Terraform Enterprise (or Terraform Cloud) private registry, linking directly to the module's registry page.
  • The import picker flags repositories that are already published to your registry, so you can spot them before importing.
  • The agent now references a module's private registry source address instead of a git URL when the module is published to the registry.

Improved

  • Registry badges resolve automatically on import, when you configure the Terraform connector, and when a new version is tagged, with no manual action needed.
  • Disabling or removing the Terraform connector immediately clears registry badges from the module catalog; re-enabling the connector restores them automatically.
v2.17.4

Fixed

  • When workspace chat is blocked, for example when you're out of credits, the message now explains the actual reason instead of a generic unavailable notice.
v2.17.3

Fixed

  • The site icon is now visible on light backgrounds, such as in Google search results.
v2.17.2

Fixed

  • CI compliance checks no longer fail unexpectedly for repositories with very large GitHub check-run IDs, which could previously cause the compliance gate to fail closed.

Showing 20 of 25