Repository navigation
feat(ci): upgrade to latest pulumi/ci-mgmt scaffolding - #350
Merged
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
ctreatma
commented
Sep 18, 2026
ctreatma
commented
Sep 18, 2026
ctreatma
force-pushed
the
pulumi-ci-mgmt
branch
3 times, most recently
from
September 23, 2026 19:49
585b069 to
b0cb73d
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. New functions:
Maintainer note: consult the runbook for dealing with any breaking changes. |
ctreatma
force-pushed
the
pulumi-ci-mgmt
branch
from
September 23, 2026 21:10
f2df0f1 to
fb44a06
Compare
ctreatma
force-pushed
the
pulumi-ci-mgmt
branch
3 times, most recently
from
September 30, 2026 19:17
1c4ae17 to
fa3cc9e
Compare
ci-mgmt's release workflow runs on tag push, replacing the semantic-release driven release workflow on main. This equinix-prefixed workflow (which ci-mgmt leaves in place) runs semantic-release in dry-run mode to determine the next version, then pushes the tag with the bot token so that the ci-mgmt release workflow is triggered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ctreatma
force-pushed
the
pulumi-ci-mgmt
branch
from
September 30, 2026 22:28
fa3cc9e to
f0dcd35
Compare
ctreatma
marked this pull request as ready for review
September 30, 2026 22:29
displague
approved these changes
Oct 1, 2026
displague
reviewed
Oct 1, 2026
| Please refer to the [main Pulumi repo](https://github.com/pulumi/pulumi/)'s [CONTRIBUTING.md file]( | ||
| https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md#developing) for details on how to get set up with Pulumi. | ||
|
|
||
| ## Updating the upstream Terraform provider version |
Member
There was a problem hiding this comment.
Does the Updating the upstream Terraform provider version section need a replacement along the lines of https://github.com/equinix/pulumi-equinix/pull/350/changes#diff-59bb78345f0191afed346e77f9583230ea1ebfe2a59275e84bfac60b5914e0b6R57-R68 (and/or -- 'call this action')
Contributor
Author
There was a problem hiding this comment.
My understanding is that the latest CI is supposed to finally deliver the original expected experience: that a new upstream provider release automatically gets pulled in without any action from anyone. Once we know what the upgrade experience is, we can document it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The provider maintenance tools used in this repo have fallen far behind what is published by Pulumi. This brings us back in line with the latest pulumi/ci-mgmt tools so that we and our customers can benefit from the various improvements Pulumi has made over the past 18 months or more.
Unfortunately, because we let this get so outdated, this upgrade is guaranteed to lead to a lot of changes in SDK files. Most of these changes are in comments and thus do not impact any end users. The remaining changes appear to be transparent changes to code structure: the new code behaves the same as the old code, it's just organized differently. I am fairly confident that I've exhausted all options to reduce the diff between the new generated code and the latest from
main.