diff --git a/.config/dotnet-tools.json b/.config/dotnet-tools.json index c6c30097..79a9fb76 100644 --- a/.config/dotnet-tools.json +++ b/.config/dotnet-tools.json @@ -3,21 +3,21 @@ "isRoot": true, "tools": { "powershell": { - "version": "7.6.5", + "version": "7.6.6", "commands": [ "pwsh" ], "rollForward": false }, "dotnet-coverage": { - "version": "18.9.0", + "version": "18.11.0", "commands": [ "dotnet-coverage" ], "rollForward": false }, "nbgv": { - "version": "3.10.91", + "version": "3.10.94", "commands": [ "nbgv" ], @@ -38,7 +38,7 @@ "rollForward": false }, "dotnet-symbol": { - "version": "9.0.661903", + "version": "10.0.731102", "commands": [ "dotnet-symbol" ], diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index c462a089..c0492a90 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -40,4 +40,4 @@ jobs: - name: Deploy to GitHub Pages id: deployment - uses: actions/deploy-pages@cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 # v5.0.0 + uses: actions/deploy-pages@368f82528645a54fb793d4d04e342629a3f51346 # v5.0.1 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index aebbffd5..4dd0c324 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -52,20 +52,6 @@ Use `nbgv tag` to create a tag for a particular commit that you mean to release. Push the tag. -### GitHub Actions - -When your repo is hosted by GitHub and you are using GitHub Actions, you should create a GitHub Release using the standard GitHub UI. -Having previously used `nbgv tag` and pushing the tag will help you identify the precise commit and name to use for this release. - -After publishing the release, the `.github/workflows/release.yml` workflow will be automatically triggered, which will: - -1. Find the most recent `.github/workflows/build.yml` GitHub workflow run of the tagged release. -1. Upload the `deployables-Linux` artifact from that workflow run to your GitHub Release. -1. Any nuget packages in the `deployables-Linux` artifact will be pushed to nuget.org. - -The workflow is written to leverage NuGet.org Trusted Publishing. -You should set `NUGET_USER` as a repo secret to satisfy Trusted Publishing requirements. - ### Azure Pipelines When your repo builds with Azure Pipelines, use the `azure-pipelines/release.yml` pipeline. diff --git a/Directory.Packages.props b/Directory.Packages.props index a1977b8a..81edc9a2 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -4,7 +4,7 @@ true true - 2.3.3 + 2.4.0 5.9.0 1.1.2 4.14.0 @@ -18,7 +18,7 @@ - + @@ -30,11 +30,11 @@ - + - + diff --git a/global.json b/global.json index 1a0684df..a7e8cbfe 100644 --- a/global.json +++ b/global.json @@ -1,6 +1,6 @@ { "sdk": { - "version": "10.0.400", + "version": "10.0.401", "rollForward": "patch", "allowPrerelease": false },