Good question. Publishing to FlakeHub makes an archive of the release, checks to make sure it evaluates cleanly in isolation, and publishes it to FlakeHub's storage.
This is to make sure that releases stay available in the long term, even through GitHub account renames or repository deletions.
This is to make sure that releases stay available in the long term, even through GitHub account renames or repository deletions.