Modernize release scripts with package updates and compatibility fixes #5318
Conversation
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
- Update all npm dependencies to latest versions: * @octokit/rest: v16.43.2 → v22.0.0 * @octokit/graphql: v7.1.1 → v9.0.1 * azure-devops-node-api: v12.0.0 → v15.1.1 * azure-pipelines-task-lib: v4.3.1 → v5.2.1 * node-getopt: v0.2.3 → v0.3.2 - Fix createReleaseBranch.js compatibility with new @octokit versions: * Remove fetch parameter from GraphQL configuration * Implement selective dry-run mode (execute git operations except push) * Improve writeAgentVersionFile to always write file - Optimize createAdoPrs.js dependencies and functionality: * Replace got v14 with Node.js native fetch API * Remove got and node-fetch dependencies completely * Fix Azure DevOps API calls to respect dry-run mode properly - Add comprehensive testing documentation: * Step-by-step testing procedures for all scripts after dependency updates * Environment setup requirements and authentication * Troubleshooting guide for common compatibility issues * Validation checklist for script updates - Comprehensive testing of all release scripts: * Verified fillReleaseNotesTemplate.js functionality * Tested rollrelease.js with GitHub PAT authentication * Validated createAdoPrs.js with improved dry-run behavior * Fixed npm audit security vulnerabilities All scripts now work correctly with updated dependencies and proper dry-run modes for safe testing.
tarunramsinghani
force-pushed
the
users/tarun/scriptfixes
branch
from
856378d to
52b3860
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
rishabhmalikMS
approved these changes
Oct 1, 2025
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.
Update all npm dependencies to latest versions:
Fix createReleaseBranch.js compatibility with new @octokit versions:
Optimize createAdoPrs.js dependencies and functionality:
Enhance util.js error handling:
Comprehensive testing of all release scripts:
All scripts now work correctly with updated dependencies and proper dry-run modes for safe testing.
Context
Explain the context or motivation behind this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items
Description
Provide a concise summary of the changes introduced in this PR.
Risk Assessment (Low / Medium / High)
Assess the risk level and justify your assessment. For example: code path sensitivity, usage scope, or backward compatibility concerns.
Unit Tests Added or Updated (Yes / No)
Indicate whether unit tests were added or modified to reflect the changes.
Additional Testing Performed
List manual or automated tests performed beyond unit tests (e.g., integration, scenario, regression).
Change Behind Feature Flag (Yes / No)
Can this change be behine feature flag, if not why?
Tech Design / Approach
Documentation Changes Required (Yes/No)
Indicate whether related documentation needs to be updated.
Logging Added/Updated (Yes/No)
Telemetry Added/Updated (Yes/No)
Rollback Scenario and Process (Yes/No)
Dependency Impact Assessed and Regression Tested (Yes/No)