Skip to content

📖 [Docs]: Document Version input accepts NuGet version ranges#38

Merged
Marius Storhaug (MariusStorhaug) merged 1 commit into
mainfrom
docs/version-input-accepts-nuget-range
Jul 10, 2026
Merged

📖 [Docs]: Document Version input accepts NuGet version ranges#38
Marius Storhaug (MariusStorhaug) merged 1 commit into
mainfrom
docs/version-input-accepts-nuget-range

Conversation

@MariusStorhaug

Copy link
Copy Markdown
Member

GitHub-Script v1.9.0 (already on main) expanded the passed-through Version input to accept a NuGet version range in addition to an exact version. This updates the Version input documentation so consumers know ranges are supported.

Changed: Version input documentation

The Version input description in action.yml (and the README input table, where present) now 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 GitHub module via GitHub-Script v1.9.0, which resolves NuGet version ranges. Mirrors the fix applied in PSModule/Release-GHRepository#106.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the GitHub Action metadata to document that the Version input supports both exact versions and NuGet version ranges, aligning the documentation with the already-shipped behavior in the referenced GitHub-Script dependency.

Changes:

  • Update Version input description to state it accepts an exact version or a NuGet version range (with an example).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@MariusStorhaug Marius Storhaug (MariusStorhaug) merged commit 634ca50 into main Jul 10, 2026
20 checks passed
@MariusStorhaug Marius Storhaug (MariusStorhaug) deleted the docs/version-input-accepts-nuget-range branch July 10, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants