Important note for any modders that use Mercurial and Bitbucket for hosting their mod downloads or version files:You've probably seen a warning about this if you've visited Bitbucket within the last few months, but just in case: Bitbucket has decided, in their infinite wisdom, to sunset Mercurial support on their platform. All existing Mercurial repositories,
including issue tracking and downloads, will be deleted after June 1st. That means if you use Bitbucket and Mercurial for source control, even if it was just to create an empty repository to host your mod downloads/version files,
you must either convert to git or another supported VCS, or move to another hosting platform, by the end of May.
Again, this will only affect you if you're using Mercurial. Git repositories are unaffected.
You can check if you'll be affected by logging in to Bitbucket and visiting this page. Any repositories listed here must be converted before June or you'll lose everything. That includes copying any downloads you wish to keep over to your new repositories, as no conversion tool I've found will include them.
I've spent the last few hours converting a few dozen of my own repositories to git and
moving them over to GitHub. GitHub has long since overtaken Bitbucket when it comes to the features available on their free plans, so it's what I would recommend if you're converting your repository anyway. GitHub's a lot less newbie-friendly, unfortunately, but since it's the most popular source hosting platform there are thousands of tutorials available online.
To move your repository from Bitbucket to GitHub, log in to GitHub and press the giant + on the top right, then Import Repository. Enter the base URL of your project (ex:
https://bitbucket.org/LazyWizard/lazylib). GitHub will handle converting your repository from Mercurial to git for you. To move your downloads over, you'll have to tag a release (if you've made commits since your last release, click "Target: master" and switch from the branch tab to recent commits, then select the commit that represents your last release), then attach the mod zip so users can download it from the releases page. For .version file hosting, I recommend modifying your version file to link to the master copy in your master branch, then only pushing a .version file update when you've released an update.