Skip to content

CI: Use specific version of action-zephyr-setup #102

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

Merged
merged 1 commit into from
May 29, 2025
Merged

CI: Use specific version of action-zephyr-setup #102

merged 1 commit into from
May 29, 2025

Conversation

d3zd3z
Copy link
Collaborator

@d3zd3z d3zd3z commented May 29, 2025

This should match the version running in the main zephyr repo.

This should match the version running in the main zephyr repo.

Signed-off-by: David Brown <[email protected]>
Copy link
Collaborator

@kartben kartben left a comment

Choose a reason for hiding this comment

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

For good measure, you'll probably want to pin all actions to SHAs

@d3zd3z
Copy link
Collaborator Author

d3zd3z commented May 29, 2025

For good measure, you'll probably want to pin all actions to SHAs

Probably good. I'm trying to figure out if these even fixes the issue I'm having. I'm seeing CI failures as it looks like the cmsis module is out of date, and I'm not sure why that is working in zephyr but not here. Unfortunately, CI runs the 'main' version not the one in the change, and it is painful to test this.

@d3zd3z d3zd3z merged commit f6e4f2c into main May 29, 2025
2 of 4 checks passed
@d3zd3z
Copy link
Collaborator Author

d3zd3z commented May 29, 2025

I'm going to merge this temporarily to test if it actually fixes the ci problem.

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