This addresses #79 and adds a workflow to help automate releases. The expectation is that the final step before a new a release would be to create a PR for an update to the Version.swift file that is used to determine the SDK version number reported to the API.
This action would be invoked manually with a required input to specify release type (patch, minor, or major):
The workflow will then:
Increment the version number in Version.swift according to the release type selected when invoking the command
Commit the change
Open a PR for the change
An example of the results of this workflow is visible here.
An alternative implementation could instead commit the change directly to main and use the new version number to tag the commit.
This addresses #79 and adds a workflow to help automate releases. The expectation is that the final step before a new a release would be to create a PR for an update to the
Version.swiftfile that is used to determine the SDK version number reported to the API.This action would be invoked manually with a required input to specify release type (patch, minor, or major):
The workflow will then:
Version.swiftaccording to the release type selected when invoking the commandAn example of the results of this workflow is visible here.
An alternative implementation could instead commit the change directly to
mainand use the new version number to tag the commit.