Tags: microsoft/kiota
Tags
ci: make release publish jobs idempotent on re-run (#7895) Re-triggering the release pipeline for a tag that was already (partially) published previously failed hard: GitHubRelease@1 returns 422 on an existing tag, NuGet push returns 409 on a duplicate version, npm/ESRP re-publish and vsce publish fail on an existing version. This blocked recovering from a partial release (e.g. when only the npm ESRP step failed) without manual surgery. Each publish job now checks whether its artifact version is already published and skips the publish step if so, otherwise publishes as before: - github_release: anonymous GitHub API lookup of the release by tag sets releaseExists; both GitHubRelease@1 tasks are gated to skip when it exists. - deploy_kiota / deploy_builder: query the nuget.org flat container for the version parsed from the .nupkg filename; 1ES.PublishNuget@1 is gated on the result. - deploy_npm: add UseNode@1 and run 'npm view @microsoft/kiota@<version>' (version parsed from the microsoft-kiota-<version>.tgz filename); EsrpRelease@12 is gated on the result. - vs_marketplace: capture vsce publish output and treat a non-zero exit whose output contains 'already exists' as an idempotent skip. PushDockerImage is already idempotent (tag overwrite) and is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
bump version for release 1.32.0 with dependency and changelog updates (… …#7753) * - bumps version for release of 1.32.0 * chore: update StreamJsonRpc and remove explicit MessagePack override * docs: add 1.32.0 entries for security fixes #7735 and #7746 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
PreviousNext