Update to v0.5.1 #310
Merged
Update to v0.5.1 #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just to confirm, the putting back into draft mode wasn't accidental, but presumably because you found the broken GitHub action issue. So I'll stand back until re-assigned 😊 |
|
Correct. Although I might have already figured out what's wrong, so it might be back with you pretty soon! |
|
Alright Guys! Thank you! I don’t think we need to meet today. Better work on things instead :-)
Cheers, Nico
… On Oct 11, 2023, at 10:48 AM, Gaurav Vaidya ***@***.***> wrote:
Correct. Although I might have already figured out what's wrong, so it might be back with you pretty soon!
—
Reply to this email directly, view it on GitHub <#310 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATJPQPBQCRLAKMWA53HSKTX62WVVANCNFSM6AAAAAA53NHLF4>.
You are receiving this because you are subscribed to this thread.
|
hlapp
approved these changes
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I forgot to increment the version number to v0.5.0 when I created that tag and release. This PR fixes that (but goes to v0.5.1 instead) and also upgrades packages using
npm upgrade.It looks like the Vite upgrade broke our GitHub publish action because it writes the website to
dist/instead ofdocs/. I've fixed this in b3e00e0.