Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding actions for generating and publishing a release #147

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

rmigneco
Copy link
Collaborator

@rmigneco rmigneco commented Nov 13, 2024

Description

Note: this pull request is based on cherry-picked commit from #139 but with develop as the base branch

The generate-release action is a manual dispatch action that takes the version number as an input, and depending on the major version, will checkout either main or main_1.x, then merge either develop or develop_1.x into it, bump all the version strings in the repo, and raise a PR against main or main_1.x.

The publish-release action runs on merge to main or main_1.x and reads the version from the version.txt file to determine the release tag it should publish, then publishes that release.

Change Notes

Pre-submission Checklist

  • I ran the unit tests locally before checking in.
  • I made sure there were no compiler warnings before checking in.
  • I have written useful documentation for all public code.
  • I have written unit tests for this new feature.

The generate-release action is a manual dispatch action that takes
the version number as an input, and depending on the major version,
will checkout either main or main_1.x, then merge either develop or
develop_1.x into it, bump all the version strings in the repo, and
raise a PR against main or main_1.x.

The publish-release action runs on merge to main or main_1.x and
reads the version from the version.txt file to determine the
release tag it should publish, then publishes that release.

NOTE: both of these actions are broken in v2 of the repo until we
bring it up to date with the Swift Package Manager support changes,
as the version.txt file does not exist in develop currently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants