Skip to content

Conversation

@TroyGarden
Copy link
Contributor

Summary:

context

  • it seems that any release branch push will trigger cpu CI
  • but (gpu) CI can't be trigger manually from github
  • the release process usually involves quite a few release push and the CI is better to handle manually.

Differential Revision: D82322377

Summary:

# context
* bump the version.txt from 1.3.0a0 to 1.4.0a0 after v1.3.0-rc1
* fix a typo in the github workflow

Reviewed By: spmex

Differential Revision: D77031187
Summary:
# context
* it seems that any release branch push will trigger cpu CI
* but (gpu) CI can't be trigger manually from github
* the release process usually involves quite a few release push and the CI is better to handle manually.

Differential Revision: D82322377
@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 12, 2025
@facebook-github-bot
Copy link
Contributor

@TroyGarden has exported this pull request. If you are a Meta employee, you can view the originating diff in D82322377.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants