docs: Add preliminary checks to release instructions - #5028
Merged
Conversation
Added a first step to verify release readiness.
johnmtll
previously approved these changes
Aug 21, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an initial “release readiness” verification step to the release instructions, improving the reliability of the driver release process.
Changes:
- Introduces a pre-flight checklist (JIRA release status, CI health, performance metrics) before starting the release workflow.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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.
Added a first step to verify release readiness.
Description
Summary of Changes
New first step for the release instructions to verify the release for readiness.
What is the motivation for this change?
More reliable releases
Double check the following
npm run check:lint)type(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript