-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Changes for 0.3.0 release #98
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! When you merge this, you'll get a 0.2.30 build on main
, but after you push the v0.3
tag to main (on the squashed merge commit), it'll build 0.3.0
and create the release in github. (hopefully ;-) )
Thanks for checking, and reminding me which tag I need to make! Will add the GitHub sponsors link and squash. |
@mikeage so close! Looks like it didn't pull the full changelog since 0.2? |
Hmmm... did you update the changelog? What's there now looks perfect... I can check the logs from the action |
Yes, I've brought in from all the other changelogs manually, it just had the single most recent change before |
Gotcha. It looks like this test wasn't correct: if [ $(git describe --tags --abbrev=0) == $(git describe --tags) ]
then
PREV=$(git describe --tags --abbrev=0 HEAD^)
else
PREV=$(git describe --tags --abbrev=0)
fi I'll check why in a little bit (going home now). Sorry about that! |
Oh, duh, of course. I copy pasted the wrong thing when I finally merge this. Will fix soon. |
Fixed in #101 (along with a bit of duplicate code removed) |
Tidy up readme, update version numbers