fix(cmd-version): fix upstream change detection to succeed w/o branch tracking - #1369
Merged
codejedi365 merged 3 commits intoNov 10, 2025
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
codejedi365
force-pushed
the
fix/upstream-verification-without-tracking-branch
branch
2 times, most recently
from
6ea2d27 to
381599b
Compare
November 10, 2025 03:40
codejedi365
force-pushed
the
fix/upstream-verification-without-tracking-branch
branch
from
381599b to
f0a0b25
Compare
November 10, 2025 04:36
codejedi365
deleted the
fix/upstream-verification-without-tracking-branch
branch
November 10, 2025 06:49
Copy link
Copy Markdown
Contributor
Author
🎉 This PR has been published as part of v10.5.1 🎉You can find more information about this release on the GitHub Releases page. |
Sorry, something went wrong.
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.
Purpose
Rationale
How did you test?
How to Verify
PR Completion Checklist
Reviewed & followed the Contributor Guidelines
Changes Implemented & Validation pipeline succeeds
Commits follow the Conventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)
Appropriate Unit tests added/updated
Appropriate End-to-End tests added/updated
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)