Ayu

I'm going to post a quick hotfix that removes the `!default` flag for all variables within the next couple hours (because this essentially BREAKS every setup which imports more than...

> Has this issue actually been fixed for usage via `@import`? Not fully nor cleanly. Arguably, it was a partial rollback of #129 so you have half a feature and...

@jwr12135, I'd be happy to add you. I actually previously wanted to get in touch with you to figure things out from before, but the lack of ways to contact...

@snigdha920, glad you're interested. I decided to move over to a Discord so more people can comfortably join without restrictions. Feel free to join us [here](https://discord.gg/UpHW6ZEyde)!

Closing in favour of #550 as this issue has a lot of outdated information.

[google-font-metadata](https://github.com/fontsource/google-font-metadata)'s V4 release adds support for this. Just needs implementation in this repo which is relatively simple once a couple other tasks are finished.

I actually have looked at Changesets before, but their process is pretty incompatible with our setup. Our entire versioning strategy would go against their Semver fundamentals. It's necessary for us...

The Next.js release process might be better to take inspiration from: https://github.com/vercel/next.js/blob/canary/release.js

This is the awkward race condition we sometimes face using Got. Sometimes running it again fixes it? I've managed to tweak the settings so it should rarely happen with Github...

The idea to integrate Fontship with Fontsource is an interesting concept but I'm not wholly sure how that will pan out practically. Exactly what would we be directly integrating? ##...