Skip to content

Commit

Permalink
Fixed the release action
Browse files Browse the repository at this point in the history
  • Loading branch information
zvonimir committed Jul 9, 2021
1 parent fa85ed6 commit 134e7c8
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 9 deletions.
4 changes: 2 additions & 2 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,9 @@ jobs:
# Restore dotnet tools
dotnet tool restore
# Build Corral
dotnet build -c Release ${SOLUTION}
dotnet build -p:Version=$VERSION -c Release ${SOLUTION}
# Create packages
dotnet pack -p:PackageVersion=$VERSION --no-build -c Release ${SOLUTION}
dotnet pack -p:Version=$VERSION --no-build -c Release ${SOLUTION}
- name: Deploy to nuget
run:
dotnet nuget push "source/Corral/bin/Release/Corral*.nupkg" -k ${{ secrets.NUGET_API_KEY }} -s https://api.nuget.org/v3/index.json
11 changes: 4 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,14 +42,11 @@ flags from the file `filename`.

## Versioning and Release

The current version of Boogie is noted in a [build property](source/Directory.Build.props).
To push a new version to nuget, perform the following steps:
To push a new version to nuget, publish a new release with a tag of the form
`vx.y.z`, where `x.y.z` is the updated version.

- Update the version (e.g., x.y.z) and commit the change
- git tag vx.y.z
- git push --atomic origin master vx.y.z

The [CI workflow](.github/workflows/test.yml) will build and push the packages.
The [release workflow](.github/workflows/release.yml) will automatically build
and push the packages.


[license-badge]: https://img.shields.io/github/license/boogie-org/corral?color=blue
Expand Down

0 comments on commit 134e7c8

Please sign in to comment.