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

Vec 228 release workflow #4

Merged
merged 14 commits into from
Jul 10, 2024
Merged

Vec 228 release workflow #4

merged 14 commits into from
Jul 10, 2024

Conversation

jdogmcsteezy
Copy link

There are 3 fields when generating a release/pre-release:

  1. The version of the release. If this is going to be an official release for version 1.0.0 then put 1.0.0. If this is going to be a snapshot of release as we progress toward the 1.0.0 release then put 1.0.0.
  2. Is this a pre-release? By clicking this box SNAPSHOT-{COMMIT} will be appended to the above version. A new tag will also be added.
  3. Delete previous pre-released? If yes the workflow will delete all pre-releases that currently exist (except the current one) that match the pattern 1.0.0-

@jdogmcsteezy jdogmcsteezy requested a review from dwelch-spike July 9, 2024 16:51
Copy link
Contributor

@dwelch-spike dwelch-spike left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming tests pass

@jdogmcsteezy jdogmcsteezy merged commit 3cb5aa3 into main Jul 10, 2024
3 checks passed
@jdogmcsteezy jdogmcsteezy deleted the VEC-228-release-workflow branch July 10, 2024 18:52
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