Shipped · DevOps and infrastructure

What pulumi/pulumi shipped

The public repository of Pulumi · github.com/pulumi/pulumi

Written by FoxPlug from the repository's own releases; not affiliated with Pulumi. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/pulumi/pulumi; Pulumi did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for pulumi, free

Week of November 2, 2026

What shipped

Why it matters

This week brings fixes that remove friction from common CLI workflows, such as environment variable crashes, stack removal messages, and global stack setup. It also improves policy management with new exception commands and richer group listings, and stabilizes resource transforms for secrets and dependencies.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: stack rm and destroy --remove now name the managed ESC environment; managed env diffs appear as engine events; fixed a PULUMI_OPTION panic; pulumi do works outside a project; pulumi api exits 3 on rejected tokens; resource transforms preserve secret Outputs and nested

Post for LinkedIn

This week we shipped several fixes and improvements for Pulumi users. The stack rm and destroy --remove commands now clearly name the managed ESC environment being deleted. Managed environment differences are shown as engine events. A panic when PULUMI_OPTION environment variables are set on typed flags is fixed. The first stateful pulumi do command works outside a project. pulumi api exits with code 3 when the access token is rejected. Resource transforms now preserve secret Output values and handle nested dependencies correctly. New experimental policy exception commands let you manage exceptions from the CLI. Policy group get now shows rule-matched members and pack configuration. Screen flickering during updates with many unchanged resources is fixed.

Week of October 26, 2026

What shipped

Why it matters

This week brings a new release alongside CLI additions for inspecting and scripting policy packs, and a fix so preview-only imports keep their generated code. It also tightens schema validation and PCL behavior so configuration and policy authors get clear errors instead of panics, dropped properties or broken SDKs.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Pulumi 3.273.0 is out. This week: pulumi policy get, JSON output for policy pack commands, preview-only imports that keep generated code, schema name-collision checks and PCL fixes for hideDiffs, invokes and label errors.

Post for LinkedIn

Pulumi 3.273.0 is out. This week the CLI gained pulumi policy get for inspecting a published policy pack, plus --output json for publish, enable, disable, rm and validate-config, with enable and disable now printing the updated group. Preview-only imports now return the engine's in-memory snapshot so generated resource code is kept. The schema binder rejects property names that collide after reduction to SDK identifiers, and PCL fixes cover hideDiffs on inputs as well as outputs, parent and pluginDownloadUrl on invokes, and a clean diagnostic for blocks without labels.

Week of October 19, 2026

What shipped

Why it matters

This week brought a new release, 3.272.0, along with two experimental commands removed and fixes for remote component outputs and skipped resources. It also extended the provider protocol with an AwaitError and added env change-request commands for working with approvals.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Pulumi 3.272.0 is out: exempted policy violations are collapsed with a flag to show them, and remote component outputs stay unknown when their children are awaiting, failed or skipped. Plus an AwaitError in the provider protocol, env change-request commands, and the experimental

Post for LinkedIn

Pulumi 3.272.0 shipped this week. Policy violations that an exception exempts now collapse into one line per policy, with --show-policy-exceptions on up and preview to list them with their exceptions. Remote component outputs that depend on a child resource which is awaiting, failed or skipped now stay unknown, so apply callbacks and dependent resources no longer run early with the wrong value. The provider protocol gains an AwaitError for operations that cannot be awaited to completion, and skipped resources under continue-on-error return dry-run outputs with unknown set. The CLI adds pulumi env change-request for working with approvals, and the experimental pulumi logs and pulumi watch commands are removed.

Week of October 12, 2026

What shipped

Why it matters

This week's releases continue the property.Value migration in plugins and add OutputValues negotiation on Call so SDKs can get per-value dependencies. Users get clearer drift reporting, safer ESC environment updates, and a leaner CLI that downloads the Java runtime on demand, while pulumi logs and pulumi watch move further along their removal schedules.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: Java runtime downloads on demand, pulumi logs and watch now error by default with opt-out variables, ESC env updates use If-Match, drift status reports unknown when it never ran, and output values negotiate on Call.

Post for LinkedIn

This week in Pulumi: the Java language runtime is no longer bundled with the CLI and is downloaded on demand the first time a runtime: java stack runs. pulumi logs and pulumi watch now return an error by default as the next step in their removal schedules, each with an environment variable to keep them running until removal. ESC environment updates now send If-Match so env edit, env set, env rm and env provider no longer overwrite changes made after they read the environment. pulumi stack drift status reports an unknown status when drift detection has never run. The PostgreSQL state backend only creates its table and index when missing, and output values are now negotiated on Call.

Week of October 5, 2026

What shipped

Why it matters

This week brings the 3.268.0 release plus a set of fixes that change what users see day to day. Policy group edits that previously reported success without applying now go through the batch endpoint, OPA policy packs install and create again, and secrets that carry dependencies are redacted in logs. New projects get smoother setup with fewer toolchain prompts, and generated Go and PCL behavior is more consistent around outputs, IDs and tuples.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Pulumi 3.268.0 is out. This week: policy group edit changes now apply, OPA policy packs run via the pulumi-language-opa plugin, secrets with dependencies are redacted in logs, ExistsResource RPC added, and pulumi new prompts less for Python and Node.js.

Post for LinkedIn

Pulumi 3.268.0 shipped this week. Alongside the release, several fixes land for people using the CLI and SDKs every day. pulumi policy group edit now sends changes through the batch endpoint, so stack, Policy Pack and Insights account edits are applied rather than silently dropped. OPA policy packs run through the pulumi-language-opa language plugin, which fixes pulumi policy new and pulumi install for them. Secret output values, including secrets carrying dependencies, are redacted in log output and logs share. A new ExistsResource RPC reports whether a resource exists without registering it in state. Generated Go and PCL code is more consistent around outputs, IDs and tuples, and pulumi new asks fewer questions when only one Python or Node.js toolchain is available.

Week of September 28, 2026

What shipped

Why it matters

This week focused on improving invoke capabilities through OutputValue negotiation, fixing state handling for assets, and enhancing observability with trace propagation. The release of v3.267.0 addresses critical issues with template cloning and Python toolchain compatibility. Numerous test parallelization improvements and code cleanup changes reduce resource leaks and port exhaustion during testing.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Pulumi v3.267.0 is out. OutputValues now supported in invokes, asset state restoration fixed, trace context propagates through backend calls, and Git tags without v prefix now work.

Post for LinkedIn

Pulumi v3.267.0 released with key improvements: OutputValues can now be negotiated in invoke requests for better dependency handling, asset contents are properly restored from state during Read/Update operations, OpenTelemetry trace context propagates through backend API calls for complete observability, and plugins can be downloaded from Git repositories using version tags without the v prefix. Also includes fixes for concurrent template operations and Python toolchain compatibility.

Week of September 21, 2026

What shipped

Why it matters

V3.265.0 brings security improvements for Windows binaries, fixes for Python code generation in complex scenarios, and better credential handling across multiple authentication contexts. The PCL interpreter and type system also received multiple correctness fixes for edge cases in tuple indexing, constant handling, and closure serialization.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V3.265.0 is out. Windows binaries now Authenticode-signed, Python output-dependent ranges fixed, and credentials key stays shared across logout/login cycles.

Post for LinkedIn

V3.265.0 released with Authenticode-signed Windows binaries to address Defender false positives, fixes for Python code generation with output-dependent resource ranges, improved credential handling across login/logout operations, and plugin/policy installation using unified atomicinstall logic.

Week of September 14, 2026

What shipped

Why it matters

V3.263.0 improves deployment settings management by adding authentication options for private repositories and preventing unintended overwrites when migrating between VCS providers. The release also fixes state handling during partial creates and protects promoted resources, while deprecating legacy commands like pulumi logs and pulumi watch.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

V3.263.0 is out. Deployment settings now support git auth for private repos, state migrations are reported, and promoted resources are protected. pulumi logs and pulumi watch are deprecated.

Post for LinkedIn

V3.263.0 released: deployment settings add git authentication flags for private repositories on any provider, state migrations are now visible in diagnostics, resources in PendingReplacement state skip deletion retries, and stacks can migrate from repo URLs to VCS integrations. We're also deprecating pulumi logs and pulumi watch commands.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-09.

Is this your repo? Ask us to remove this page.