Repository navigation
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: equinix/pulumi-equinix
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.32.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: equinix/pulumi-equinix
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.33.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 2,456 files changed
- 2 contributors
Commits on Sep 30, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 1952216 - Browse repository at this point
Copy the full SHA 1952216View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7401e39 - Browse repository at this point
Copy the full SHA 7401e39View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5d82ace - Browse repository at this point
Copy the full SHA 5d82aceView commit details -
Configuration menu - View commit details
-
Copy full SHA for 10d07c8 - Browse repository at this point
Copy the full SHA 10d07c8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1f17d5a - Browse repository at this point
Copy the full SHA 1f17d5aView commit details -
add workflow to tag releases with semantic-release
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>
Configuration menu - View commit details
-
Copy full SHA for 753c420 - Browse repository at this point
Copy the full SHA 753c420View commit details -
Configuration menu - View commit details
-
Copy full SHA for f618168 - Browse repository at this point
Copy the full SHA f618168View commit details -
Configuration menu - View commit details
-
Copy full SHA for f0dcd35 - Browse repository at this point
Copy the full SHA f0dcd35View commit details
Commits on Oct 1, 2026
-
feat(ci): upgrade to latest pulumi/ci-mgmt scaffolding (#350)
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`.
Configuration menu - View commit details
-
Copy full SHA for f9769f6 - Browse repository at this point
Copy the full SHA f9769f6View commit details -
ci: push release tags with the automation token
actions/checkout persists GITHUB_TOKEN as an http.extraheader, and git sends that header instead of the credentials in the tag push URL. The v0.33.0 tag was therefore pushed with GITHUB_TOKEN, and pushes made with GITHUB_TOKEN don't trigger other workflows, so release.yml never ran. Don't persist credentials on checkout, so the tag push authenticates with PULUMI_PROVIDER_AUTOMATION_TOKEN. semantic-release builds its own authenticated URL from GITHUB_TOKEN, so it doesn't need them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 0b73bc2 - Browse repository at this point
Copy the full SHA 0b73bc2View commit details -
ci: push release tags with the automation token (#357)
## Summary The `equinix-tag-release` workflow created the `v0.33.0` tag, but the tag push didn't trigger `release.yml`. `actions/checkout` persists `GITHUB_TOKEN` (default `persist-credentials: true`) as an `http.https://github.com/.extraheader` `AUTHORIZATION` header, and git sends that header instead of the credentials in the push URL. So the tag was pushed with `GITHUB_TOKEN` rather than `PULUMI_PROVIDER_AUTOMATION_TOKEN`, and [events triggered by `GITHUB_TOKEN` don't start other workflows](https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow). This sets `persist-credentials: false` on the checkout, so the push authenticates with the automation token from the push URL. semantic-release's dry run is unaffected: it builds its own authenticated URL from the `GITHUB_TOKEN` in its environment. It also keeps the automation token out of the git config, so the semantic-release step (which installs packages from npm at runtime) can't read it. ## After merging `release.yml` only runs on tag pushes, so `v0.33.0` needs to be pushed again to trigger it: either delete the remote tag and push it from a user account, or delete it and re-run `equinix-tag-release`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Configuration menu - View commit details
-
Copy full SHA for 301489d - Browse repository at this point
Copy the full SHA 301489dView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.32.3...v0.33.0