Retry rollback #505
Retry rollback #505
Conversation
Signed-off-by: Kingdon P Barrett <kingdon@tuesdaystudios.com>
|
That commit should have just rolled everything back to v0.24.3 state, now I'm going to put some things back in package.json, CONTRIBUTING.md, CHANGELOG.md, etc. as I've mentioned above. |
Signed-off-by: Kingdon P Barrett <kingdon@tuesdaystudios.com>
Signed-off-by: Kingdon P Barrett <kingdon@tuesdaystudios.com>
|
The prerelease channel now shows v0.26.x version that has rolled back successfully. I'm going to throw the release in main now, we'll have v0.27.0 that does not include any features or updates since v0.24.3. Please stay tuned for a prerelease later this week where we'll attempt again to push the live update changes. Whether you'll need to be on a pinned vscode release to use them, or if we can resolve the issues with the upstream changes, is still TBD. In the mean time, if you're missing the live update function, you can pin VSCode to v1.84.2 and use v0.26.0 GitOps Tools. |
The solution in #504 was not correct. I'm glad I stopped the stream before I got to this part...
Git wizardry is hard. I'm going to try again, only this time I'm going to try not to roll back all the docs updates or workflow fixes that we had done since 0.24.3 (since none of those fixes are relevant for the rollback!)
The release that just went out to edge/prerelease is not fixing anything. Bear with me...