Skip to content

[DO NOT MERGE] Update MODULE.bazel#4316

Open
frankzha-dev wants to merge 1 commit into
pytorch:mainfrom
frankzha-dev:main
Open

[DO NOT MERGE] Update MODULE.bazel#4316
frankzha-dev wants to merge 1 commit into
pytorch:mainfrom
frankzha-dev:main

Conversation

@frankzha-dev
Copy link
Copy Markdown

Cuda version change from 13.0 to 13.2 as we are about to upgrade to that version

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant and/or add your own.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project (You can use the linters)
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas and hacks
  • I have made corresponding changes to the documentation
  • I have added tests to verify my fix or my feature
  • New and existing unit tests pass locally with my changes
  • I have added the relevant labels to my PR in so that relevant reviewers are notified

Cuda version change from 13.0 to 13.2 as we are about to upgrade to that version
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented Jun 2, 2026

Hi @frankzha-dev!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@github-actions github-actions Bot added the component: build system Issues re: Build system label Jun 2, 2026
@lanluo-nvidia
Copy link
Copy Markdown
Collaborator

@frankzha-dev
this is already in:
567ba6a
please close your PR

@frankzha-dev
Copy link
Copy Markdown
Author

The purpose of this PR is to get Meta to approve CLA. Will close it afterwards.

@narendasan
Copy link
Copy Markdown
Collaborator

yes @lanluo-nvidia just a placeholder to monitor @frankzha-dev's onboarding

@narendasan narendasan changed the title Update MODULE.bazel [DO NOT MERGE] Update MODULE.bazel Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: build system Issues re: Build system

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants