Closed SkyeHoefling closed 2 years ago
Release tagging was completed as part of https://github.com/FileOnQ/Imaging.Heif/compare/97770ece5694e7ce69d963eea629e69bc965eafa...7cbbf526c614b315c2df0a2fbb618e977060a72d with #32.
The main build has a new trigger that checks for tagged builds with v*
or v*-preview-*
on:
push:
branches: [ main ]
tags: [ 'v*', 'v*-preview-*']
Our release tagging process is as follows. When it is time to release you create 3 number semantic version tag. For example version 1 will be 1.0.0
. The tag created will be v1.0.0
Closing out this issue as the work is completed and had to be pushed directly to main as it was build work
Description
Add new GitHub Actions to release final NuGets based on git tagging strategy
v1.0.0
1.0.0