This repository was archived by the owner on Jul 16, 2026. It is now read-only.
📖 [Docs]: Document Version input accepts NuGet version ranges#25
Closed
Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
Closed
📖 [Docs]: Document Version input accepts NuGet version ranges#25Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
Version input accepts NuGet version ranges#25Marius Storhaug (MariusStorhaug) wants to merge 3 commits into
Conversation
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 10, 2026 08:42
View session
There was a problem hiding this comment.
Pull request overview
Updates the action documentation to reflect that the Version input supports NuGet version ranges (in addition to exact versions), matching the already-shipped behavior via GitHub-Script v1.9.0.
Changes:
- Update
README.mdinput table to document NuGet version range support forVersion. - Update
action.ymlinput description to document NuGet version range support forVersion.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| README.md | Updates the Version input documentation in the README inputs table to mention NuGet version ranges. |
| action.yml | Updates the Version input description to state that exact versions and NuGet version ranges are accepted. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…onical Version doc
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
July 10, 2026 08:52
View session
Marius Storhaug (MariusStorhaug)
deleted the
docs/version-input-accepts-nuget-range
branch
July 16, 2026 17:58
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
GitHub-Script v1.9.0 (already on
main) expanded the passed-throughVersioninput to accept a NuGet version range in addition to an exact version. This updates theVersioninput description inaction.ymlso consumers know ranges are supported.Changed:
Versioninput documentationThe
Versioninput description inaction.ymlnow states that it accepts an exact version or a NuGet version range (for example[1.2.0, 2.0.0)), instead of claiming the value must be an exact version.Technical Details
Documentation-only; no behavior change. The action already installs the
GitHubmodule via GitHub-Script v1.9.0, which resolves NuGet version ranges. The README input table in this repo uses an aligned (padded) format enforced by markdownlint MD060, so it is left unchanged here to avoid a full-table reformat —action.ymlis the canonical input documentation shown in the GitHub Actions UI. Mirrors the fix in PSModule/Release-GHRepository#106.