Skip to content

Automated upgrade: bump pulumi/pulumi to 3.255.0 - #3110

Closed
pulumi-bot wants to merge 2 commits into
masterfrom
update-pulumi/30545354856-284
Closed

Automated upgrade: bump pulumi/pulumi to 3.255.0#3110
pulumi-bot wants to merge 2 commits into
masterfrom
update-pulumi/30545354856-284

Conversation

@pulumi-bot

Copy link
Copy Markdown
Contributor

Automated upgrade: bump pulumi/pulumi to 3.255.0

@eon-pulumi

eon-pulumi Bot commented Jul 30, 2026

Copy link
Copy Markdown

Review Verdict: Comment Only

Mechanical pulumi/pulumi 3.253.0 to 3.255.0 bump; version applied uniformly across all six go.mod files and .pulumi.version, and go mod verify passes for provider and sdk. Held at COMMENT rather than APPROVE only because required lint and prerequisites checks were still in progress at review time (none failing). Automated low-risk assessment, not a human review.


View session · Was this review helpful? Yes · No

@eon-pulumi-agent eon-pulumi-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated low-risk assessment, not a human review.

Mechanical dependency bump of pulumi/pulumi from 3.253.0 to 3.255.0 (plus transitive updates: go-logr, go-isatty, go-runewidth, otel collector, genproto, grpc; drops the now-unused atotto/clipboard and golang.org/x/exp indirect deps). The diff is confined to .pulumi.version and the go.mod/go.sum files across the provider, sdk, and examples modules — no hand-written or generated Go/schema/SDK source is touched.

What I checked:

  • The 3.255.0 version is applied uniformly across all six go.mod files and .pulumi.version; no straggler on the old version.
  • go mod verify passes for both the provider and sdk modules.
  • No behavior change beyond the dependency version.

Holding at COMMENT rather than APPROVE only because the required lint and prerequisites checks were still in progress at review time (no required check is failing, and warn_codegen / Update Changelog are green). Once those complete green this is safe to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant