Merged
Conversation
Signed-off-by: Tyler Cloutier <cloutiertyler@users.noreply.github.com>
Centril
added a commit
that referenced
this pull request
Aug 22, 2024
1 task
bfops
pushed a commit
that referenced
this pull request
Jul 16, 2025
* Upgraded module to 0.12 * 0.12 upgrade is working * Fixes * Fixed some server warnings * Small fix * Apply suggestions from code review * Update Cargo.toml * Package upgraded to 0.12.0 * Renamed SampleScene => Main --------- Co-authored-by: John Detter <no-reply@boppygames.gg> Co-authored-by: Tyler Cloutier <cloutiertyler@users.noreply.github.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 2, 2026
# Description of Changes <!-- Please describe your change, mention any related tickets, and so on here. --> Copied from: #4084 We originally reverted this because it was causing testsuite flakes in private. Now we have solved the issue that was causing the flakes so this should be safe to merge. Version upgrade to `v1.12.0`. # API and ABI breaking changes <!-- If this is an API or ABI breaking change, please apply the corresponding GitHub label. --> None # Expected complexity level and risk 1 - this is just a version upgrade <!-- How complicated do you think these changes are? Grade on a scale from 1 to 5, where 1 is a trivial change, and 5 is a deep-reaching and complex change. This complexity rating applies not only to the complexity apparent in the diff, but also to its interactions with existing and future code. If you answered more than a 2, explain what is complex about the PR, and what other components it interacts with in potentially concerning ways. --> # Testing <!-- Describe any testing you've done, and any testing you'd like your reviewers to do, so that you're confident that all the changes work as expected! --> The testsuite failures are fixed by #4120 - [x] License has been properly updated including version number and date - [x] CI passes --------- Co-authored-by: John Detter <4099508+jdetter@users.noreply.github.com> Co-authored-by: rekhoff <r.ekhoff@clockworklabs.io> Co-authored-by: clockwork-labs-bot <clockwork-labs-bot@users.noreply.github.com> Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 2, 2026
# Description of Changes <!-- Please describe your change, mention any related tickets, and so on here. --> Copied from: #4084 We originally reverted this because it was causing testsuite flakes in private. Now we have solved the issue that was causing the flakes so this should be safe to merge. Version upgrade to `v1.12.0`. # API and ABI breaking changes <!-- If this is an API or ABI breaking change, please apply the corresponding GitHub label. --> None # Expected complexity level and risk 1 - this is just a version upgrade <!-- How complicated do you think these changes are? Grade on a scale from 1 to 5, where 1 is a trivial change, and 5 is a deep-reaching and complex change. This complexity rating applies not only to the complexity apparent in the diff, but also to its interactions with existing and future code. If you answered more than a 2, explain what is complex about the PR, and what other components it interacts with in potentially concerning ways. --> # Testing <!-- Describe any testing you've done, and any testing you'd like your reviewers to do, so that you're confident that all the changes work as expected! --> The testsuite failures are fixed by #4120 - [x] License has been properly updated including version number and date - [x] CI passes --------- Co-authored-by: John Detter <4099508+jdetter@users.noreply.github.com> Co-authored-by: rekhoff <r.ekhoff@clockworklabs.io> Co-authored-by: clockwork-labs-bot <clockwork-labs-bot@users.noreply.github.com> Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 2, 2026
# Description of Changes <!-- Please describe your change, mention any related tickets, and so on here. --> Copied from: #4084 We originally reverted this because it was causing testsuite flakes in private. Now we have solved the issue that was causing the flakes so this should be safe to merge. Version upgrade to `v1.12.0`. # API and ABI breaking changes <!-- If this is an API or ABI breaking change, please apply the corresponding GitHub label. --> None # Expected complexity level and risk 1 - this is just a version upgrade <!-- How complicated do you think these changes are? Grade on a scale from 1 to 5, where 1 is a trivial change, and 5 is a deep-reaching and complex change. This complexity rating applies not only to the complexity apparent in the diff, but also to its interactions with existing and future code. If you answered more than a 2, explain what is complex about the PR, and what other components it interacts with in potentially concerning ways. --> # Testing <!-- Describe any testing you've done, and any testing you'd like your reviewers to do, so that you're confident that all the changes work as expected! --> The testsuite failures are fixed by #4120 - [x] License has been properly updated including version number and date - [x] CI passes --------- Co-authored-by: John Detter <4099508+jdetter@users.noreply.github.com> Co-authored-by: rekhoff <r.ekhoff@clockworklabs.io> Co-authored-by: clockwork-labs-bot <clockwork-labs-bot@users.noreply.github.com> Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 2, 2026
# Description of Changes <!-- Please describe your change, mention any related tickets, and so on here. --> Copied from: #4084 We originally reverted this because it was causing testsuite flakes in private. Now we have solved the issue that was causing the flakes so this should be safe to merge. Version upgrade to `v1.12.0`. # API and ABI breaking changes <!-- If this is an API or ABI breaking change, please apply the corresponding GitHub label. --> None # Expected complexity level and risk 1 - this is just a version upgrade <!-- How complicated do you think these changes are? Grade on a scale from 1 to 5, where 1 is a trivial change, and 5 is a deep-reaching and complex change. This complexity rating applies not only to the complexity apparent in the diff, but also to its interactions with existing and future code. If you answered more than a 2, explain what is complex about the PR, and what other components it interacts with in potentially concerning ways. --> # Testing <!-- Describe any testing you've done, and any testing you'd like your reviewers to do, so that you're confident that all the changes work as expected! --> The testsuite failures are fixed by #4120 - [x] License has been properly updated including version number and date - [x] CI passes --------- Co-authored-by: John Detter <4099508+jdetter@users.noreply.github.com> Co-authored-by: rekhoff <r.ekhoff@clockworklabs.io> Co-authored-by: clockwork-labs-bot <clockwork-labs-bot@users.noreply.github.com> Co-authored-by: Zeke Foppa <bfops@users.noreply.github.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
API
If the API is breaking, please state below what will break