Skip to content

Commit

Permalink
v0.6.0
Browse files Browse the repository at this point in the history
  • Loading branch information
xt0rted committed Apr 10, 2024
1 parent 1d97b0e commit f81460a
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 3 deletions.
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

## Unreleased

## [0.6.0](https://github.com/xt0rted/dotnet-run-script/compare/v0.5.0...v0.6.0) - 2024-04-10

- Dropped support for .NET Core 3.1
- Dropped Support for .NET 6
- Added support for .NET 8
Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ dotnet new tool-manifest
dotnet tool install run-script
```

> **Warning**
> [!WARNING]
> Installing this tool globally is not recommended.
> PowerShell defines the alias `r` for the `Invoke-History` command which prevents this from being called.
> You'll also run into issues calling this from your scripts since global tools don't use the `dotnet` prefix.
Expand Down Expand Up @@ -68,7 +68,7 @@ In your project's `global.json` add a `scripts` object:
```jsonc
{
"sdk": {
"version": "6.0.100",
"version": "8.0.203",
"rollForward": "latestPatch"
},
"scriptShell": "pwsh", // Optional
Expand All @@ -80,7 +80,7 @@ In your project's `global.json` add a `scripts` object:
}
```

> **Note**
> [!NOTE]
> The shell used depends on the OS.
> On Windows `CMD` is used, on Linux, macOS, and WSL `sh` is used.
> This can be overridden by setting the `scriptShell` property or by passing the `--script-shell` option with the name of the shell to use.
Expand Down

0 comments on commit f81460a

Please sign in to comment.