Repository navigation
fix(release): show planned version in release decision prompt - #661
Merged
Merged
Conversation
added 2 commits
August 12, 2026 17:20
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6d909fae-8b84-4214-b4b3-be9c99c7b155
…t-dev-gh/reveal-plan
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the interactive release-planning prompt to include the already-planned change type and version transition when the user is choosing whether to keep the existing plan (option 2). This improves decision clarity during the pre-release review loop.
Changes:
- Extend release “finding” objects to carry planned/current version and effective change/target version when the package is already in the resolved release set.
- Update
Format-PackageMenuto append(change-type: from -> to)to option 2 when those plan details are available (and keep legacy wording when they aren’t). - Add/adjust Pester unit tests to validate the new prompt output and ensure plan details propagate into findings.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| scripts/tests/Pester/unit/release-crate/PromptFlow.Tests.ps1 | Updates test finding builders and adds coverage for option 2 showing planned version transition + legacy fallback. |
| scripts/lib/releasing.ps1 | Propagates planned/effective version metadata into findings returned by Get-UnreleasedModifiedDependencies and documents the new fields. |
| scripts/lib/release-flow.ps1 | Updates Format-PackageMenu to include the planned change/version hint on option 2 when present; wires planned fields into manual SemVer review findings. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #661 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 473 473
Lines 45913 45913
=======================================
Hits 45913 45913 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Sander Saares (sandersaares)
approved these changes
Aug 13, 2026
martintmk
approved these changes
Aug 13, 2026
martintmk
added a commit
that referenced
this pull request
Aug 13, 2026
main advanced with #661 (show planned version in release decision prompt), which modified release-flow.ps1, PromptFlow.Tests.ps1 and two releasing.ps1 functions (New-ResolvedReleaseSetFromBaseRef, Get-UnreleasedModifiedDependencies). All of those belong to the plan engine this branch retires, so the deletions win and the trimmed releasing.ps1 is kept. Full Pester suite (146) green post-merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 59264f5d-db1f-4379-9cc3-6663f2914b90
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.
Summary
Show the existing release plan’s change type and version transition in option 2 of the package release decision prompt.
Before:
After:
This lets users understand the effect of keeping the planned release level before making a decision.
Fixes AB#7705528