-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix github actions deprecation warnings + preflight checks #12
Conversation
humbletim
commented
Oct 23, 2022
•
edited
Loading
edited
- update action dependencies to avoid deprecation warnings
- add more error checking and preflight checks around SDK webservice assumptions
bump actions/cache to v3
bump actions/checkout to v2.5.0
reference points:
|
temporarily enable tsmate
Could we merge this? @humbletim |
Guess a year between reminders is ok @humbletim |
Can you merge this @humbletim ? |
Hi.. I am (somewhat) back again and in any event planning to get this PR merged this week. Apologies for the delay. Also if anyone is interested in adopting lead responsibility for the project or helping to co-maintain please let me know. |
Don't worry. I could help you out 😃 |
Thank you @humbletim ! This is awesome! |
README.md
Outdated
- 1.3.204.1 | ||
- 1.3.211.0 | ||
- 1.3.216.0 | ||
- 1.3.224.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.3.275.0
is already out.
Hi everyone! There seems to be a recent issue building SPIRV-Tools on macOS. While unrelated to this PR, I typically run a final "CI build" on different platforms before releasing. Unfortunately, Mac builds are failing for all but the the latest SDK version, apparent due to To understand the scope of the problem, I'd appreciate it if anyone using the SDK on Mac could share:
I'm planning to merge this PR to "main" later tonight after one final non-mac-legacy CI test, but am thinking to hold off on stamping an official release tag until I have a clearer picture of the Mac issue. Once I gather more information, I plan to file an issue report and potentially involve relevant teams for a resolution. Thanks for your input! |