Data and AI releases

548 this month · 176 companies

Pulumi, May 2026 new features

7 releases · 1 product

Pulumi Service Provider v1.0

The Pulumi Service Provider has officially reached v1.0 and is now generated from the public Pulumi Cloud OpenAPI specification , which commits to a stable contract for the existing resource surface and keeps the provider up to date automatically.

Update
Source ↗

Clearer edit and review modes for ESC change requests

Pulumi ESC change requests now cleanly separate editing a draft from reviewing one. The editor is always where you change the new version, the approval page is a read-only diff, and a banner on the environment lets you flip between the two.

Update
Source ↗

View team membership from the Members tab

The Members tab in Access Management now shows which teams each member of your organization belongs to. Before, you had to open each team individually to see who was on it; now the full picture is on one page, under Settings > Access Management > Members . Visit the Pulumi Cloud console to have a look.

Update
Source ↗

A refreshed Pulumi Cloud console

The Pulumi Cloud console has a refreshed look: new colors; more consistent controls like inputs, selects, and buttons; a new collapsible sidebar with condensed hierarchical navigation; new layouts for tabular data; a new resource graph display; and much more. Check it out at https://app.pulumi.com and let us know what you think!

Update
Source ↗

Neo task notifications

Neo can now notify you when a task needs your input, either through native desktop notifications, an audible sound, or both. As you delegate more tasks to Neo and work more asynchronously, you’ll know right away whenever Neo is finished and waiting for you. You can enable Neo task notifications in Account settings > Neo settings in the Pulumi Cloud console .

Update
Source ↗

Connect any Git or Mercurial repo with Custom VCS

Custom VCS integrations connect any Git or Mercurial version control system to Pulumi Cloud, including self-hosted and third-party servers. Store your authentication credentials (SSH, basic auth, or a personal access token) in a Pulumi ESC environment, point the integration at your VCS server, and push to your repository to trigger Pulumi Deployments.

Update
Source ↗