I migrated my plugin’s repository from Github to Codeberg. My plan is only to keep Github for releasing new versions of my plugin. To do that I created a Github action in my old repo that does several things when called:
- Fetch all tags from Codeberg
- Push them to Github
- For each tag that does not have a release on Github, create a draft release
- Build the main.js and upload it together with styles and manifest to the draft
- Publish the release
This all looks fine at first glance but my last releases cannot be found by Obsidian. For 1.6.1 I can somehow understand (main.js was missing first and was added later manually) but 1.6.2 should have worked quite fine.
Any ideas what’s going wrong here? Am I missing something?
Thanks for response!
So this means that I still have to update the mainfest.json in my Github repo for a new release? Is that the only place that needs to stay in sync? (versions.json and package.json also contain the version number). I wonder why the release’s manifest.json is not used instead.
manifest.json is read from the main/master branch, so Obsidian knows what is the latest release version.
versions.json is read to determine which release versions compatible with which Obsidian version.
After that, finally GitHub releases are taken to find the latest available release version for the specific Obsidian version
1 Like
Ah okay thanks. So am I correct to assume that I could delete everything but the manifest and versions json files and then just keep releases/tags on Github? I’d like to have this a clean a possible 
Nice, everything looks fine now. I’m still doing some testing and cleanup, but my main problem (the update not showing up) is solved, thanks!