Originally created by: dwmkerr
We need to publish to npm on release as well as bumping version numbers
Originally posted by: benib
@dwmkerr can you maybe do a npm publish now to push 0.6.0 until this issue is resolved? Thanks for your effort.
npm publish
You seem to have CSS turned off. Please don't fill out this field.
Originally posted by: dwmkerr
@benib done 😄
thanks. I stumpled upon this package that seems to do a good job: https://github.com/boennemann/semantic-release
Ideal solution:
build
dst
This way PRs don't need to include dst changes and they'll be easier to merge.
Log in to post a comment.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: benib
@dwmkerr can you maybe do a
npm publishnow to push 0.6.0 until this issue is resolved? Thanks for your effort.View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: dwmkerr
@benib done 😄
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: benib
thanks. I stumpled upon this package that seems to do a good job: https://github.com/boennemann/semantic-release
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: dwmkerr
Ideal solution:
buildfolder, not thedstfolder.dstfolder.This way PRs don't need to include
dstchanges and they'll be easier to merge.