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.

Sign up for GitHub

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

Jump to bottom

Fix/Determine pre-release tags and pipelines #1738

Closed
turetske opened this issue Nov 15, 2024 · 1 comment · Fixed by #1827
Closed

Fix/Determine pre-release tags and pipelines #1738

turetske opened this issue Nov 15, 2024 · 1 comment · Fixed by #1827
Assignees
@CannonLock
Labels
infrastructure GitHub Actions, Release management, and CI

Comments

@turetske
Copy link
Collaborator

Currently our pre-releases have the same tags as the release, we want to ensure that they get some sort of altered tag such as: vX.Y.Z-pre-release or vX.Y.Z-alpha and in order to ensure our conda-forge builds don't use them until we get a release

Things that would be important:

  1. Have a check to ensure our pre-release workflows fail if they don't have those semantics
  2. Have a check to ensure our release workflows fail if they have that semantic tag
@CannonLock
Copy link
Contributor

@jhiemstrawisc You did this correct?

@jhiemstrawisc jhiemstrawisc linked a pull request Jan 10, 2025 that will close this issue
Trigger release actions if tag matches new -rc.X prerelease tags #1827
Merged
@jhiemstrawisc jhiemstrawisc added the infrastructure GitHub Actions, Release management, and CI label Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CannonLock CannonLock

Labels
infrastructure GitHub Actions, Release management, and CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Trigger release actions if tag matches new -rc.X prerelease tags jhiemstrawisc/pelican
3 participants
@turetske @CannonLock @jhiemstrawisc