Closed JoelAnderson-UU closed 1 year ago
Sorry, I screwed up the release.... you should still be able to get 2.0.1 using BRAT because it's a pre-release. 2.0.2 was so buggy on my device that I decided to just delete the release. Going to release 2.1 in a few days, so if you'd like, you can wait for that. Otherwise, I'll send you the files for 2.0.2. It might have only been bugging for me.
No worries! I've backtracked to 1.3, and that's working for now. I'll just await the 2.1 update. I'll just need to watch that it doesn't get updated the next time I install updates on all 100 community plugins I have installed! 🫣
perhaps best to change the manifest again to an older version, atm you get a update message in obisidian and then the issue that you can't update the plugin.
that's really odd,
this is the latest release. I guess Obsidian doesn't update it when I delete a release. I'll have to ask in the Discord. Was planning on finishing it up today, but I was out all day. Sorry about that!
Obsidian shows this because it tries to download a tag 2.0.2 from GitHub even though it doesn't exist.
Maybe I can force update 1.3.3 to latest release? I just gave it a try. Usually it takes a few minutes to update in the community store.
Argh! I'm so sorry y'all, but I accidentally deleted the local copy of 2.1 :sob:
I'm not even joking... I was trying to test install the version from the plugin store, but I used the wrong vault and it permanently deleted my working copy of the plugin! For now, I guess I'll have to release 2.0.1 because 2.0.2 is still broken. Will be even more delays until 2.1 :((( but as long as you don't need "created today" and "deleted today" headings, 2.0.1 should suffice
Nevermind, 2.0.2 works. Just had a problem on my end. Going to just release this, and you should be able to use it in the meantime! 2.0.2 also added an option for intervals between writes.
2.0.2 released here. Give it a few minutes to update in Obsidian, and the issue should be fixed. I'm so sorry that 2.1 is taking so long! Something always seems to go wrong. Completely my fault for deleting the wrong thing and neglecting backups... but it's okay, now I have an excuse to re-write the thing
I know the nausea which overcomes somebody that you did something totally stupid after you figure it out.. thanks for the updates will look into it. BTW: Obsidian will look into the manifest.json for a version which it then pulls from the releases, so to roll back to an older version you just need to put that older version into your manifest.json again. And it will also only look into the version from the main branch. If you want to have a "beta" you can utilize BRAT and add a manifest-beta.json which a different version number, but that and the releases must still be in the main branch
I know the nausea which overcomes somebody that you did something totally stupid after you figure it out.. thanks for the updates will look into it. BTW: Obsidian will look into the manifest.json for a version which it then pulls from the releases, so to roll back to an older version you just need to put that older version into your manifest.json again. And it will also only look into the version from the main branch. If you want to have a "beta" you can utilize BRAT and add a manifest-beta.json which a different version number, but that and the releases must still be in the main branch
That's cool! Thanks for letting me know! 2.0.2 seems to have no bugs anyway, so I figured I'd just take it out of beta. Previously, I just had the beta under "pre-release" without its version in the mainest.json, and you could still get it from BRAT.
I had falsely believed 2.0.2 was broken because my daily note format was messed up. Enjoy for now!!
First Steps
Describe the bug
Could not update from 1.x to 2.0.2 so I uninstalled, and now I cannot install version 2.0.2 on Obsidian v1.0.3 running a MacBookPro with Ventura.