[Ramses Sanchez-Hernandez (ramsessanchez)]

A similar PR may already be submitted! Please search among the Pull request before creating one.

Thanks for submitting a pull request! Please provide enough information so that others can review your pull request.

NOTE: PR's will be accepted only in case of appropriate information is provided below

Summary

Upgrade the production pipeline from EsrpRelease@9 to EsrpRelease@14 and update CONTRIBUTING.md. All authentication inputs, package inputs, and release conditions remain unchanged.

Motivation

Explain the motivation for making this change. What existing problem does the pull request solve?

The v3.1.0 release retry in Azure DevOps run 260454 passed the build stage but failed before ESRP authentication: v9 requires a Node 16 handler blocked by the agent's EOL policy. Installed ESRP v14.0.0 uses a Node20_1 handler. Comparing the installed v9/v14 input schemas found no required migration for the existing npm/certificate-authentication configuration.

Test plan

Demonstrate the code is solid. Example: The exact commands you ran and their output.

• git diff --check — passed.
• az devops invoke --organization https://dev.azure.com/microsoftgraph --area distributedtask --resource tasks --api-version 7.0 --query 'value[?name==EsrpRelease && version.major==14].{version:version,execution:execution}' --output json — passed; confirmed installed v14.0.0 uses Node20_1.
• A Python comparison against HEAD passed: the pipeline's only change is EsrpRelease@9 to EsrpRelease@14; inputs and release conditions are unchanged.
• Documented npm run build, npm run test, and npm run lint were not run: this changes only the release-task version and documentation, not SDK code; Node.js/dependencies are unavailable in this worktree.
• Azure pipeline execution and live authentication/publication were not run. Manual validation is build-only and does not execute the gated publishing stage. Existing run retries retain the original YAML, so retrying the old release run alone will not adopt this upgrade.

Closing issues

N/A.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.