-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying 'latest' as dotnet-version #497
Labels
feature request
New feature or request to improve the current logic
Comments
CamJN
added
feature request
New feature or request to improve the current logic
needs triage
labels
Jan 10, 2024
Hello @CamJN, |
I'd also appreciate this feature. For reference, it is currently possible to install the latest LTS version with: - name: Setup .NET
uses: actions/setup-dotnet@v4
with:
dotnet-version: x Unfortunately, this always installs a version from the LTS channel due to Lines 77 to 78 in 3e891b0
|
kevinoid
added a commit
to kevinoid/NetCoreProject
that referenced
this issue
Nov 20, 2024
The version must be specified explicitly due to actions/setup-dotnet#497 (comment) Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
kevinoid
added a commit
to kevinoid/NLCaseConvert
that referenced
this issue
Nov 20, 2024
The version must be specified explicitly due to actions/setup-dotnet#497 (comment) Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
A workflow with the following would install the latest major version of dotnet.
Justification:
It would be nice to be able to just stick
latest
in the dotnet-version field and not have to update the tag when a new major version comes out. This is available in the node and ruby setup actions and is quite nice.Are you willing to submit a PR?
Unlikely.
The text was updated successfully, but these errors were encountered: