🔔 We're looking for new maintainers to help get Gryphon back on track!
If you're interested (or know someone who is), head to the link below:
https://t.co/WDP0VZMt1Z
The good news is Gryphon was designed with this in mind from the start, so at least I’ll sleep well at night knowing your Android apps can go on without it.
It’s been a pleasure, y’all 😄
I’m still considering transferring management to some folks from the community (if that sounds like you, let me know!)
If that doesn’t pan out I’ll retire the repo in a month or two (but leave it open for forks, etc in case anyone wants to keep going)
Also, concerning @gryphonblog: I’ve decided to step down from maintaining the project. I no longer have the time or energy to do it the way it needs to be done.
I'll be going on a short vacation around the new year, and when I come back (hopefully with a clear head) I'll decide if I go back to maintaining the project properly or if I officially close the main fork
A few bugs with the Xcode 13.3+ integration have already been fixed, but since there's no telling how many more are left, it was worth releasing an early version with Swift 5.6 support.
If in doubt, avoid running `gryphon init` if possible, and keep Xcode 13.2.1 around.
Support for Xcode 13.3+ is still under development. A lot changed in xcodebuild's output, and the information isn't structured the way Gryphon expects it anymore. Because of that it's hard to know exactly how much of the Xcode integration is working at the moment.
@gryphonblog I think the new build system will be the last problem to solve (it happened at the end of the last test) but it’s an Xcode issue so I do need a MacBook to fix it, unfortunately.
Update on @gryphonblog support for Swift 5.6: I decided to abandon the Bootstrapping tests that were causing most issues, and was almost done supporting the new build system in Xcode 13.3, when my MacBook broke down.
Sorry folks, it’s gonna be a while still.
Removing it might cause some bugs to be missed in future releases, but I’m having a hard time finding a way to keep it around.
Which is to say: this might take a while.
Update on Swift 5.6 support: it’s mostly done, but it’s causing major problems for the bootstrapping test, which is the codebase’s most comprehensive test by far
@rrenna@vvendra The issue with Swift 5.6 unfortunately is with using it to compile Gryphon itself, not with any new features your code might use.
I hope to have a fix in the next week or so, but you can also download Swift 5.5, build Gryphon with it, then use it with Swift 5.6 in your code.
Hey folks, just to let y’all know that I am planning on helping out with the recent issues on Gryphon’s GitHub + supporting the newly-released Swift 5.6.
I am also, however, _extremely overwhelmed_ right now, possibly burning out, so I appreciate your patience and understanding.
Version v0.18.1 is out!
https://t.co/DudN8AmWog…
🐞 This fixes a compilation issue that was happening in Xcode 13. Thanks @Guizones for reporting it and @xwu for helping me fix it in the Swift forums.