Skip to content

Commit d2be914

Browse files
committed
Removed 'if' check in release-package job, removed debug output and updated README.md
1 parent a18d5a0 commit d2be914

File tree

2 files changed

+22
-14
lines changed

2 files changed

+22
-14
lines changed

.github/workflows/release-package.yml

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ env:
99

1010
jobs:
1111
release-serviurtium-core:
12-
if: ${{ contains(github.ref, 'refs/tags/servirtium.core/v') }}
1312
runs-on: ubuntu-latest
1413

1514
steps:
@@ -27,20 +26,11 @@ jobs:
2726
- name: Test
2827
run: dotnet test --no-restore --verbosity normal
2928

30-
# - name: Determine Version
31-
# uses: paulhatch/semantic-version@v4.0.2
32-
# id: semantic_version
33-
# with:
34-
# format: "${major}.${minor}.${patch}-dev.{increment}"
35-
3629
- uses: nuget/setup-nuget@v1
3730
with:
3831
nuget-api-key: ${{ secrets.NuGetAPIKey }}
3932
nuget-version: '5.x'
40-
- name: Dump GitHub context
41-
env:
42-
GITHUB_CONTEXT: ${{ toJSON(github) }}
43-
run: echo "$GITHUB_CONTEXT"
33+
4434
- name: Extract version from ref
4535
uses: actions/github-script@v4
4636
id: extract-version

README.md

Lines changed: 21 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,8 +89,8 @@ See `deploy_local_nuget.sh `
8989
9090
## Published NuGet assemblies
9191
92-
* [Servirtium.Core/1.0.0](https://www.nuget.org/packages/Servirtium.Core/1.0.0)
93-
* [Servirtium.AspNetCore/1.0.0](https://www.nuget.org/packages/Servirtium.AspNetCore/1.0.0)
92+
* [Servirtium.Core/1.3.0](https://www.nuget.org/packages/Servirtium.Core/1.3.0)
93+
* [Servirtium.AspNetCore/1.3.0](https://www.nuget.org/packages/Servirtium.AspNetCore/1.3.0)
9494
9595
## Current Status
9696
@@ -104,4 +104,22 @@ Current roadmap in priority order:
104104
105105
## Confirming compatability with other implementations
106106
107-
Read about the [compatibility suite](COMPATIBILITY_SUITE.md) for this .NET implementation
107+
Read about the [compatibility suite](COMPATIBILITY_SUITE.md) for this .NET implementation
108+
109+
## Releasing New Versions
110+
111+
Releases are pushed using the `release-package.yml` Github action, which is triggered by creating a Github release
112+
113+
To publish a new version of the Servirtium.Core package:
114+
115+
1. Create & Publish a new Github release from the web UI, with the tag Servirtium.Core/v<semver2-version> - the tag can be created in advance or be new as part of the release, but the package will only be pushed when a release is created in either case.
116+
2. The release-package.yml workflow should pick up this new release and push a nuget package.
117+
118+
To publish a new version of the Servirtium.AspNetCore package:
119+
120+
1. Create & Publish a new Github release from the web UI, with the tag Servirtium.AspNetCore/v<semver2-version> - the tag can be created in advance or be new as part of the release, but the package will only be pushed when a release is created in either case.
121+
2. The release-package.yml workflow should pick up this new release and push a nuget package.
122+
123+
The release-package.yml workflow is generic, it will publish any package you name prior to the forward slash, provided there is a directory in the root of the source with that name containing a csproj file with the same name.
124+
125+
e.g. You could create a release tagged `Apoplectic.Turkeys/v1.2.3` - if there is a project at `/Apoplectic.Turkeys/Apoplectic.Turkeys.csproj` in the source, it will pack and push package Apoplectic.Turkeys version 1.2.3. Otherwise the workflow will fail and nothing will happen

0 commit comments

Comments
 (0)