Repository navigation
Publish GitHub releases automatically when the version changes - #57
Merged
Merged
Conversation
Add a release workflow that builds and zips GChan with packageRelease.ps1 and publishes it as a GitHub release whenever <Version> in GChan.csproj changes on develop. A version with a suffix (e.g. 6.6.0-beta) becomes a pre-release, and the notes list the commits since the previous v* tag. Pull requests touching the build get a build-only run, and the workflow can be run by hand to retry a release or as a dry run. Make <Version> the only version to bump: AssemblyVersion and FileVersion are now derived from it. Make packageRelease.ps1 fail when publishing fails, read the project's own <Version> rather than the first one in the file, and hand its results to the workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces building, zipping and uploading releases by hand.
How to release: bump
<Version>inGChan/GChan.csprojand get it ontodevelop. The workflow then:packageRelease.ps1(same zip as before,GChan<version>.zip);v<version>and publishes a GitHub release with the zip attached;6.6.0-beta), otherwise as the latest release;v*tag, which you can edit on GitHub afterwards.It only releases when the version actually changes in a push, and never re-uses an existing tag. Other changes to the project file just build.
Also:
<Version>is now the only version to bump;AssemblyVersionandFileVersionare derived from it (still6.5.0.0for the current version).packageRelease.ps1now stops ifdotnet publishfails, instead of zipping an empty folder.🤖 Generated with Claude Code