0.10.11 updates (READY) #36
Merged
Conversation
This file contains 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
up to date with Animated Smoke Ring commit (5f85d80adca77c5adb1e207ef3390b4231924edf), ensure no names have been changed before finishing up
ditto
ditto 2
misplacedm erganser fixed
we missed one!
Hai Legacy
|
I totally thought Hai Legacy would be merged after the Avgi, haha. My mistake. |
Let's see if I can figure out how to make this work!
|
And here we are. Should be all set! |
Saugia
reviewed
Jan 20, 2025
oops Co-authored-by: Saugia <[email protected]>
|
All set? |
Unless I missed something else, and unless something else relevant gets merged (unlikely, I feel); this should be ready for when 0.10.11 actually goes out! |
TheGiraffe3
reviewed
Jan 21, 2025
They're down as "Voidfish" in my ES data folder? |
|
Are we good to merge this now, or did I miss something else? |
TheGiraffe3
approved these changes
Feb 1, 2025
tibetiroka
approved these changes
Feb 1, 2025
Of course! ^_^ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Figured I might as well set up the PR, even though we're... a couple weeks out, I think? Prevent duplication of work, and all. This PR should cover all changes for 0.10.11, please tell me or fix it if I'm missing something! I also have a separate branch on my repo for Avgi stuff in the event that that's ready for 0.10.11, but we'll see- it is currently not included here.