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

Bump Jimver/cuda-toolkit from 0.2.14 to 0.2.15 #796

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 22, 2024

Bumps Jimver/cuda-toolkit from 0.2.14 to 0.2.15.

Release notes

Sourced from Jimver/cuda-toolkit's releases.

v0.2.15

What's Changed

New Contributors

Full Changelog: Jimver/cuda-toolkit@v0.2.14...v0.2.15

Commits
  • d34c721 Update dist
  • 206bd0f Only set executable directory to downloadDirectory if undefined
  • 386cdbd Add typescrip-eslint/eslint-plugin package
  • 4c69e73 Use npm ci instead if npm i
  • 0975aa2 Update dist
  • 67636ff Update action version to 0.2.15
  • 93411bd Update dist
  • c537add Bump semver and @​types/semver
  • 11910f4 Bump @​actions/artifact from 2.0.1 to 2.1.5
  • 4b80dee Bump @​typescript-eslint/parser from 6.18.1 to 7.7.0
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [Jimver/cuda-toolkit](https://github.com/jimver/cuda-toolkit) from 0.2.14 to 0.2.15.
- [Release notes](https://github.com/jimver/cuda-toolkit/releases)
- [Commits](Jimver/cuda-toolkit@v0.2.14...v0.2.15)

---
updated-dependencies:
- dependency-name: Jimver/cuda-toolkit
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 22, 2024
@mmuetzel
Copy link
Contributor

Updating this action to a newer version looks good to me.

The new version added support for installing a newer version of CUDA (version 12.4.0 and 12.4.1). Should we also bump the version of CUDA that is installed in the CI after this is merged?

@DrTimothyAldenDavis DrTimothyAldenDavis merged commit 00fd53a into dev Apr 27, 2024
50 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/Jimver/cuda-toolkit-0.2.15 branch April 27, 2024 20:53
@DrTimothyAldenDavis
Copy link
Owner

Yes, I'll bump the cuda version. It looks like it only appears explicitly in the root-cmakelists.yaml.

@mmuetzel
Copy link
Contributor

Yeah. That should be the only place where the CUDA version is set.

It looks like there is an installation error for newer versions of CUDA though. (The CI is failing on that step.) Might be this upstream issue:
Jimver/cuda-toolkit#263

Should the CUDA version bump be reverted until that is fixed?

@DrTimothyAldenDavis
Copy link
Owner

I'll go ahead and revert both of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants