Due to complications caused by the CurseForge packager not always playing ball, changing over to the BigWigs Packager will allow us to become CurseForge independent and packaging will be more reliable.
Before changing, we would need to update the GitHub project settings and add the API key for CF.
Then disable the CF project automatic packaging option so we avoid running the old packaging process.
Once the pull request is merged into the main branch we can like before create releases by pushing a tag to the repo, then the new action will package the addon and publish it to CF directly from GitHub.
Future tagged releases will also be finalized on GitHub, meaning any tags for content substitution, localization, changelog, and so on, will be properly generated when publishing, so other addon clients can directly fetch the releases from GitHub as well as a positive side-effect of this change.
Due to complications caused by the CurseForge packager not always playing ball, changing over to the BigWigs Packager will allow us to become CurseForge independent and packaging will be more reliable.
Before changing, we would need to update the GitHub project settings and add the API key for CF. Then disable the CF project automatic packaging option so we avoid running the old packaging process.
Once the pull request is merged into the main branch we can like before create releases by pushing a tag to the repo, then the new action will package the addon and publish it to CF directly from GitHub.
Future tagged releases will also be finalized on GitHub, meaning any tags for content substitution, localization, changelog, and so on, will be properly generated when publishing, so other addon clients can directly fetch the releases from GitHub as well as a positive side-effect of this change.