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

Follow pulumi's weekly shipped digest

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-10-13.

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