Track which stacks use a specific Pulumi package and at what versions, or upgrade a stack to the latest version of a package. Use when users ask about package version tracking, outdated package versions across stacks, upgrade candidates, or package usage audits. Also use when users want to upgrade/update a specific package version in a stack or project. Do NOT use for general infrastructure creation, resource provisioning, or questions about how to use a package.
GET /api/registry/packages?name={package_name}&orgLogin={orgName}
You must include the orgLogin parameter with the user's organization name. The response contains a packages array. Each entry has a version field (the latest version), plus name, publisher, source, and packageStatus.
GET /api/orgs/{orgName}/packages/usage?packageName={package_name}
Replace {orgName} with the organization name from context or the PULUMI_ORG environment variable.
Response fields:
packageName: The queried packagestacks: Array of {stackName, projectName, version, lastUpdate}totalStacks: Total countUse when the user wants to know which stacks are using an outdated version of a package.
version against the latest to identify outdated stacksUse when the user wants to upgrade a specific stack/project to the latest version of a package.
runtime field in Pulumi.yaml, then update the correct dependency file:
nodejs → package.jsonpython → requirements.txt or pyproject.tomlgo → go.modyaml → Pulumi.yamlpulumi preview to catch any breaking changes introduced by the version bump before merging.