-
Notifications
You must be signed in to change notification settings - Fork 887
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish release 0.2.0 #955
Comments
@deining - I also created tag |
Oops, somehow I had the wrong commit. That is fixed now: |
Duhh, the Lines 5 to 9 in f7b37a0
We should have corrected this first in a new commit and then tagged this commit, I guess. This way, the tags for modules Anyway, our actions crossed and I just updated #849. This issue mentions a few items that need to be addressed IMHO. |
@deining - Thanks for the updated notes. We're still learning. I've deleted the release and will start again tomorrow or Wednesday (I don't have time tonight). Could you make the updates you mention in the previous comment? Sorry to all for the fuss. I'm sure that it'll go better the next time around. |
That's very true!
Done with #958. I will go through the whole documented installation process tomorrow to make sure everything works as expected.
Yes, certainly! |
I double checked all module installation methods and made some minor improvements on the way, see #958. For me, everything ran smoothly and worked out as expected. Looking forward to the release of version |
Looking forward to the release of version |
Tags created (from the current HEAD). |
Hopefully, we'll be able to close a few more of the 22Q1 milestone items before the release.
dependencies/v0.2.0
package.json
- NPM package: change version to 0.2.0 #961The text was updated successfully, but these errors were encountered: