Skip to main content

Releases

October 2026

  • CLI and SDK rollup: Automation API commands, resourceExists, and more

    We shipped a bunch of new features and improvements in the Pulumi CLI and SDK this month. A few highlights:

    • A big expansion of the generated Automation API for Node.js, Python, and Go, adding version, whoami, install, state, env, up, and logs commands (v3.268, v3.271, v3.273)
    • A new resourceExists built-in — and generated exists methods — that check whether a resource with a given ID exists without adopting it into your stack (v3.273)
    • Version 2 of the --policy-pack-config format, which nests policy configuration under policies and adds an exceptions field, plus a --show-policy-exceptions flag for pulumi up and pulumi preview (v3.271, v3.272)
    • New pulumi env change-request commands for reviewing, approving, and applying ESC change requests from the CLI (v3.272)
    • Fixes to pulumi org audit-log so it honors --user and --event-type, moves to the V2 audit log API, and adds --end-time (v3.271)

    We also retired the deprecated pulumi watch command and the bare pulumi logs command in favor of its subcommands (v3.273).

    See the Releases page on GitHub for the full list.

    — Christian Nunciato

  • New built-in roles for Pulumi Cloud

    Pulumi Cloud has a new set of built-in roles — Reader, Builder, and Maintainer — that map more cleanly to how teams actually work, from someone who just needs to look around to someone who owns and administers a resource. We’ve also added an organization-wide default role, so new members start with exactly the access you intend, and updated the access management UI to make all of this easier to see and change.

    You’ll find it under your organization’s access settings in the Pulumi Cloud console. To learn more, see the role documentation.

    — Christian Nunciato

  • Manage Pulumi ESC change requests from the CLI

    You can now work with Pulumi ESC change requests directly from the CLI. The new pulumi env change-request commands let you open a change request, review its diff, comment, approve or unapprove, and apply it — all without leaving your terminal.

    Terminal window
    # List open change requests for an environment
    pulumi env change-request list --env myproject/myenv -o myorg
    # Review the proposed diff
    pulumi env change-request diff <id>
    # Approve and apply it
    pulumi env change-request approve <id>
    pulumi env change-request apply <id>

    To learn more, read the announcement post or the pulumi env change-request documentation.

    — Christian Nunciato

  • AI infrastructure on tap with the Pulumi AICR provider

    The new Pulumi NVIDIA AI Cluster Runtime (AICR) provider lets you stand up pre-validated GPU training and inference clusters across clouds in just a few lines of Python. Instead of wiring together the dozens of resources a production AI cluster needs, you describe the cluster you want and let the provider assemble it.

    If you’re building self-hosted AI infrastructure, it’s a great time to try it out.

    To learn more, read the announcement post.

    — Christian Nunciato

  • Assign policy groups by stack and account tags

    Policy groups can now match stacks and cloud accounts by tag, instead of only by explicit assignment. Add a tag rule to a policy group, and any stack or account that carries a matching tag is covered automatically — including new ones created later, which pick up the right policies as soon as they join the group.

    This keeps policy coverage from drifting as your environment grows: tag your infrastructure the way you already do, and the policies follow.

    You can define tag rules in the Pulumi Cloud console or from the CLI with pulumi policy group new and pulumi policy group edit. To learn more, read the announcement post.

    — Christian Nunciato

  • Pulumi ESC now issues OIDC tokens for any service

    Pulumi ESC can now sign short-lived OIDC tokens for any service, not just the clouds it already integrates with. Set the audience you need, and ESC issues a token with a stable subject you can pin in that service’s trust policy — so you can authenticate to any OIDC-aware system with a credential that expires instead of a long-lived secret.

    To learn more, read the announcement post or the custom audience documentation.

    — Christian Nunciato

  • Concurrent change requests in Pulumi ESC

    Pulumi ESC change requests now support concurrent edits. More than one person can open a change request against the same environment at the same time, review and approve independently, and apply their changes without waiting for someone else’s request to land first.

    This makes change requests far more practical for busy teams sharing a single environment, where several people often need to propose updates in parallel.

    To learn more, read the announcement post.

    — Christian Nunciato

  • Google Cloud provider v10

    Version 10 of the Pulumi Google Cloud provider is now available. It brings the provider up to date with the latest upstream resources and APIs, along with the usual round of fixes and improvements.

    Because this is a major version, some resources and properties have changed in breaking ways. To make the upgrade as painless as possible, we’ve published a migration guide — and an agent skill that can do much of the work for you.

    To learn more, read the announcement post.

    — Christian Nunciato

September 2026

  • CLI and SDK rollup: Richer deployment settings and more

    We shipped a bunch of new features and improvements in the Pulumi CLI and SDK this month. A few highlights:

    • A much more capable pulumi deployment settings edit that can now configure git authentication, dependency caching, template sources, drift remediation, tag triggers, review stacks, and the version control integration (v3.262, v3.263, v3.264)
    • pulumi state promote now protects the resources it retains, so a subsequent update can’t delete them before the generated code lands in your program (v3.263)
    • A pulumi logout --all --delete-credentials-key option to remove the key that encrypts your stored credentials from the OS credential store (v3.265)
    • Authenticode-signed Windows CLI and language-host binaries (v3.265)
    • Support for importing a pulumi:index:Stash resource (v3.262)
    • Slightly faster startup across all commands (v3.264)

    … plus a long list of PCL, program-generation, and SDK fixes, and the foundations for component state migrations across the engine and the Go, Python, and Node.js SDKs. See the Releases page on GitHub for details.

    — Christian Nunciato

  • Change your components, keep your infrastructure

    You can now ship breaking changes to a reusable Pulumi component without forcing a replacement of the infrastructure it manages. Component state migrations let you attach a callback to a component that rewrites its state as the component’s shape changes — splitting a resource in two, renaming a child, or moving managed state around — so existing stacks upgrade cleanly instead of destroying and recreating resources.

    Migrations are available through resource options in Go, Python, and Node.js, run automatically on the next update, and are reported as part of your regular preview and update diagnostics.

    To learn more, read the announcement post or the state migrations documentation.

    — Christian Nunciato

  • Custom agents for Pulumi Neo

    You can now create named custom agents in Pulumi Neo. Instead of one general-purpose assistant, you can define purpose-built agents — each with its own configuration and scope — and run them on the tasks they’re suited for, from the Pulumi Cloud console or as part of an automation.

    Give an agent a name, configure how it works, and it’s ready to take on real infrastructure work on your behalf.

    To learn more, see the custom agents documentation.

    — Christian Nunciato

  • Policy violations now appear in pull request comments and checks

    When a preview or update runs with a policy pack, the pull request comment and commit check that Pulumi Cloud posts now include a Policy violations section. It shows how many mandatory and advisory violations were found, then lists each one with its policy pack, policy name, the resource it flagged, and the violation message. Developers can now view why a preview failed from their pull request without opening Pulumi Cloud.

    The section appears on GitHub, GitLab, Bitbucket, and Azure DevOps, for previews as well as updates. Pull request comments list up to 40 violations; check run details include the full list.

    See the version control integrations and policy docs for details.

    — Michael Fallihee

  • Set up cloud OIDC from the Pulumi CLI

    You can now configure keyless cloud authentication without leaving your terminal. The new pulumi env setup command sets up OIDC trust for AWS, Azure, or Google Cloud and creates the Pulumi ESC environments that use it, so your stacks and deployments can pull short-lived cloud credentials instead of storing long-lived secrets.

    Terminal window
    pulumi env setup aws

    The command prompts for anything you don’t pass as flags, such as which policy to attach and which accounts or projects to cover, then prints everything it created when it’s done.

    To learn more, read the announcement post or the pulumi env setup documentation.

    — Christian Nunciato

August 2026

August 2026 release

Full support for Terraform state, cross-language modules, and HCL

Manage your Terraform state, publish and share Terraform modules across languages, and write programs in HCL as a first-class Pulumi language.

HCL, Terraform state, and Terraform modules converging on the Pulumi mark
  • CLI and SDK rollup: pulumi new, pulumi do, and more

    We shipped a bunch of new features and improvements in the Pulumi CLI and SDK this month. A few highlights:

    • A redesigned interactive pulumi new that asks for a cloud provider and language instead of listing every template, then confirms your project, stack, and config defaults in a single step (v3.258, v3.259)
    • Opt-in encryption of stored credentials with a key protected by your operating system, selected with PULUMI_CREDENTIAL_STORE (v3.258)
    • A new pulumi state get command to inspect an individual resource in your state (v3.257)
    • A new pulumi state promote command that turns the stateful snippets created by pulumi do into Pulumi program code (v3.260)
    • An --ignore-protect flag for pulumi up, pulumi preview, and pulumi destroy that deletes protected resources without unprotecting them in state first (v3.256)
    • Full-stack validation for Go policy packs via policyx.NewStackValidationPolicy (v3.258)
    • A PULUMI_DEFAULT_ORGANIZATION environment variable to set your default organization (v3.259)
    • Support for Go 1.27 (v3.260)

    We also retired the AI mode of pulumi new in favor of pulumi neo (v3.256), and made a raft of improvements to pulumi do as well.

    See the Releases page on GitHub and the pulumi do docs for details.

    — Christian Nunciato

  • EnterpriseBusiness Critical

    Query your infrastructure with the Pulumi Context API

    The Pulumi Context API is now available in public preview. It connects everything Pulumi knows about your infrastructure, the resources your programs manage, the dependencies between them, how stacks consume each other’s outputs, and the resources Discovery finds in your cloud accounts, into a queryable graph.

    Pulumi Neo uses the Context API out of the box. Any other agent, including Claude Code, Codex, and Cursor, learns what it needs to get started with a Markdown document served by the graph API.

    Check out the announcement blog post for the full story.

    — Levi Blackstone

  • Experimental Rust support for Pulumi

    Pulumi Labs has released pulumi-rust, an experimental Rust SDK and language plugin for the Pulumi platform. If you’ve been waiting to write your infrastructure in Rust, you can now give it a try.

    This is an early-stage, experimental project: there are no promises of official support yet, and the API is still taking shape. But it’s a great time to kick the tires — tinker with it, file issues, and open pull requests to help shape where it goes.

    To get started, head over to the pulumi-rust repository on GitHub.

    — Christian Nunciato

  • Stateful, zero-setup resource operations with pulumi do

    You can now use pulumi do to create, read, update, and delete cloud resources directly from the command line — no program, project, or stack required — and pull them into new or existing Pulumi projects when you’re ready. Resources created with pulumi do are tracked and managed transparently for you, so commands like these just work:

    Terminal window
    # Create a new resource
    pulumi do aws:s3:Bucket create my-bucket
    # Update the resource in place
    pulumi do aws:s3:Bucket patch my-bucket
    # Delete it
    pulumi do aws:s3:Bucket delete my-bucket

    When the time comes to pull these resources into a proper Pulumi project of your own, you can promote them using the new pulumi state promote command:

    Terminal window
    pulumi state promote my-bucket

    All of this makes pulumi do a unified, consistent API across the whole cloud that agents can use to manage resources easily and directly, without you having to give up the benefits of a solid IaC foundation.

    pulumi do is generally available as of v3.258.0. To learn more, read the announcement post or the pulumi do documentation.

    — Christian Nunciato

  • A notification center for Pulumi Cloud

    The Pulumi Cloud console now has a unified inbox for all of your notifications. You’ll find it in the sidebar, just above the name of the active organization, and it notifies you in real time, no reload required:

    The notification center

    The new notification center currently covers Neo tasks, ESC approvals, and billing notifications, and we’ll be adding more notification types, including token usage, in the weeks ahead. There’s also a full-page view of your notifications that lets you manage them more easily.

    You can adjust your notification preferences — including whether to be notified in the console, by email, or both — on your Account settings page.

    — Christian Nunciato

July 2026

  • TeamEnterpriseBusiness Critical

    Migrate CloudFormation and ARM with discovered stacks

    Pulumi Cloud now discovers your AWS CloudFormation stacks and Azure Resource Manager deployments as discovered stacks. When Pulumi Discovery scans your cloud accounts, every stack and deployment appears with its resources, each mapped to its Pulumi shape and carrying a migration status computed from live state so it never gets stale.

    When you’re ready to bring them under Pulumi management, the migration path is built in: hand it to Neo, generate import commands from the console, or drive the same flow from your own agent through the REST API. Progress is derived from real state, and the migration is done when a zero-diff pulumi preview proves the code matches the cloud. Pulumi-hosted Terraform stacks get the same treatment through a new Migration tab.

    Read the announcement blog post or the discovered stacks documentation to learn more, and follow the step-by-step migration tutorial to take a CloudFormation stack all the way to Pulumi.

    — Alejandro Cotroneo

  • Pulumi Kubernetes Operator v2.8.0

    This release contains critical fixes for destroyOnFinalize, making stack teardown and reconciliation more reliable. It also contains quality-of-life feature additions such as better error condition messaging and allowing the flux source artifact size to be configurable.

    For the full list of changes, see the v2.8.0 release notes on GitHub.

    — Guinevere Saenger

  • Async Python program entrypoints with pulumi.run

    Pulumi Python programs can now use an async entrypoint. Pass a zero-argument async function to pulumi.run in your __main__.py, and the runtime awaits it on the program’s event loop. This makes it easier to call async functions while retaining a linear program flow:

    import pulumi
    async def main() -> pulumi.Inputs:
    value_a = await some_async_operation()
    value_b = await some_other_async_operation()
    return {"value_a": value_a, "value_b": value_b}
    pulumi.run(main)

    If the entrypoint returns a mapping, each entry is registered as a stack output, merging with any explicit pulumi.export calls using the normal export behavior. The entrypoint can also return None and call pulumi.export directly.

    pulumi.run may be called only once per program, and existing synchronous programs keep working unchanged. For details, see the async entrypoint documentation.

    — Julien Poissonnier

  • Bulk cloud account onboarding for Discovery

    You can now connect your AWS, Azure, and Google Cloud accounts to Pulumi Discovery in bulk. The new Connect cloud accounts wizard discovers the accounts in your AWS organization, Azure tenant, or Google Cloud organization and helps you connect them to Discovery. With the recommended authentication options, no long-lived cloud secrets are stored in Pulumi Cloud.

    Onboarding used to mean manual OIDC configuration and a hand-written Pulumi ESC environment for every account, which made complete coverage across hundreds of accounts, subscriptions, and projects hard to reach. The wizard takes a whole batch across all three clouds from disconnected to scanning in a few minutes.

    Bulk onboarding is available now to organization admins and members with permission to connect cloud accounts. Read the announcement blog post or the Connect cloud accounts documentation to learn more.

    — Levi Blackstone

  • Improved pnpm support for Node.js projects

    If you manage your Node.js Pulumi projects with pnpm, our latest releases make the experience a lot smoother:

    • Pulumi now supports pnpm 11, including its stricter handling of post-install scripts, so pulumi new works out of the box with the latest pnpm (#23815)
    • Serialized functions no longer embed pnpm’s versioned store paths in require calls, so upgrading a dependency no longer produces spurious diffs in serialized code, or errors when a dynamic provider loads its dependencies during pulumi refresh or pulumi destroy (#23767)
    • Magic functions, callbacks written inline in your program and deployed as cloud functions, like an aws.lambda.CallbackFunction, now work in pnpm projects. Symlinked workspace and file: dependencies are fixed the same way (#23866)

    After you upgrade to an SDK with these fixes, expect a one-time diff on previously serialized functions as their require paths switch to the new version-independent form.

    For more on how Pulumi serializes functions in Node.js, see the function serialization docs.

    — Julien Poissonnier

  • Usage limits for Pulumi Neo

    You can now set monthly usage limits for Pulumi Neo to help keep your costs under control as you use Neo to handle more infrastructure tasks.

    Organizations with Neo enabled can set a single dollar limit for the entire organization or individual limits for org members. You can also set up email notifications to be notified at 50%, 80%, and 95% of your configured limits.

    The Manage token usage panel, where an admin sets the organization's monthly Neo limit and turns on email notifications

    Neo usage limits are available now for all organizations, and are configurable by organization admins and billing managers. Read the announcement blog post or the usage limits documentation to learn more.

    — Christian Nunciato

  • Passkey support in Pulumi Cloud

    If you sign into Pulumi Cloud with an email and password, you can now sign in with a passkey as well. A passkey is a public-key credential stored on your device (your phone, laptop, hardware key, or password manager) that lets you sign in securely without having to enter a password.

    Saving a new passkey in Pulumi Cloud

    Passkeys are available to all users of Pulumi Cloud. Read the announcement blog post or visit your account settings to set up your first passkey.

    — Christian Nunciato

  • Versioned CLI and SDK docs

    Pinned to an older Pulumi CLI or SDK version and finding that the docs describe a newer release? The CLI command reference and the SDK API docs now include a version selector, so the documentation you’re reading matches the version you’re actually running. We keep immutable snapshots going back to v3.150.0, covering the CLI and the Node.js, Python, .NET, and Java SDKs, and your selection is sticky as you navigate.

    Read the announcement blog post or head straight to the CLI command reference to try the version dropdown.

    — Christian Nunciato

June 2026

May 2026

May 2026 release

Building for agentic infrastructure

As agents take on more of the work of infrastructure, they need tools that meet them where they are.

Agent surfaces — Claude Code, OpenCode, Codex, and Pulumi Neo — around the Pulumi mark
  • 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.

    This release also adds:

    • Fine-grained RBAC as code
    • Pulumi IDP (internal developer platform) as code
    • Audit-log export as code

    The release is live on npm, PyPI, NuGet, Maven Central, and pkg.go.dev.

    To learn more about this release, read the announcement post, and check out the provider’s documentation in the Pulumi Registry. See the v1.0.0 release notes for additional details.

    — Christian Nunciato

  • EnterpriseBusiness Critical

    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. Both modes are deep-linkable, so you can send a coworker a URL to review — or co-edit — the same draft before it’s approved.

    Learn more about approvals in Pulumi ESC.

    — Christian Nunciato

  • 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!

    — Christian Nunciato

  • 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.

    — Christian Nunciato

  • 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. Pulumi Neo can also clone and push to these repositories using the same credentials.

    To learn more, read the announcement post, and to set up your first integration, check out the Custom VCS documentation.

    — Christian Nunciato

The infrastructure platform for humans and agents.