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

Use latest release ci #237

Merged
merged 4 commits into from
Feb 2, 2025
Merged

Use latest release ci #237

merged 4 commits into from
Feb 2, 2025

Conversation

casparvl
Copy link
Collaborator

No description provided.

@casparvl casparvl added this to the v0.5.1 milestone Jan 30, 2025
@casparvl casparvl mentioned this pull request Jan 30, 2025
1 task
Copy link
Collaborator

@smoors smoors left a comment

Choose a reason for hiding this comment

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

lgtm, haven't tested myself, but i'm sure you did :)

EDIT: 2 checks are failing

@boegel
Copy link
Contributor

boegel commented Jan 31, 2025

@casparvl Looks like some of the CI worklflows need to be updated accordingly?

@smoors
Copy link
Collaborator

smoors commented Jan 31, 2025

@casparvl Looks like some of the CI worklflows need to be updated accordingly?

@boegel PR already opened for scorecard, see my comment above ;)

@casparvl
Copy link
Collaborator Author

casparvl commented Feb 1, 2025

@smoors @boegel fixed. Test is simply no longer relevant. The CI does already do a check for the fallback version against the latest tag.

@smoors smoors merged commit 1949e5e into EESSI:main Feb 2, 2025
17 checks passed
@casparvl casparvl deleted the use_latest_release_ci branch March 4, 2025 16:47
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.

3 participants