Closed haani-niyaz closed 2 years ago
Thanks, @haani-niyaz and @mridulganga for the help. @haani-niyaz have you added the comment to trigger the semantic releaser and make it v0.2.0? I am approving the PR, can you merge it if the comment message is apt. I saw that none of the other commits bumped the bug-fix versions as expected. Maybe, there is a need to encourage members to follow the commit message rules to trigger releases accordingly,
Thanks, @haani-niyaz and @mridulganga for the help. @haani-niyaz have you added the comment to trigger the semantic releaser and make it v0.2.0? I am approving the PR, can you merge it if the comment message is apt. I saw that none of the other commits bumped the bug-fix versions as expected. Maybe, there is a need to encourage members to follow the commit message rules to trigger releases accordingly,
@shukra-in-spirit, I was planning on merging #45 to this PR as it completes the v0.2.0
release requirements. Once done, I'll bump this with a feat
commit to trigger v0.2.0
I saw that none of the other commits bumped the bug-fix versions as expected.
Do you mean with the fix
type in the commit message or something else?
I also think some release planning is in order to keep everyone on the same page.
Yeap. With a fix mention in the comment to bump up the x in v0.1.x
Yeap. With a fix mention in the comment to bump up the x in v0.1.x
@shukra-in-spirit, I don't see any commits with fix
type in the main
branch's commit log. Possibly squashed when merging.
:tada: This issue has been resolved in version 0.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Change Summary
Docs update
Closes #44
Limit builds
on:pull_request
sinceon:push
results are available in the PR and this will avoid duplicate runsAddresses #43
Dockerfile enhancements
Closes #45 .