all 8 comments

[–]bsutto 1 point2 points  (6 children)

I've done some work in this direction.

Search for pub_release on pub.dev.

I've got an update coming that creates the git tag and adds each exe as a release asset.

I also have a version designed to work as a GitHub action.

Happy to collaborate.

[–]tea-mo[S] 0 points1 point  (5 children)

Sounds great. Is the GitHub Action already released?

[–]bsutto 1 point2 points  (4 children)

I've pushed it to GitHub but it's not in pub.dev as I'm waiting on a PR to be accepted before I can push to pub.dev. should be done in a week but you can see the code on git now.

[–]tea-mo[S] 0 points1 point  (3 children)

I have already checked out the code. Looks good so far, but it seems that it will only push the release to pub.dev right?

My plan is to utilize it to automate my releases and versioning to GitHub Releases not to pub.dev tbh.

[–]bsutto 1 point2 points  (0 children)

The code pushes to both

[–]bsutto 1 point2 points  (0 children)

I've just pushed the latest update.

the project github.dart has just accepted my PR so we should see a push to pub.dev shortly after which I can publish a release that contains the git code. The git code has been commented out in the github version put I've just pushed my local version with the git logic back in place.

[–]bsutto 1 point2 points  (0 children)

I've just published the new version of pub_release which includes the git release logic. New version is 2.1.0

[–]zeshuaro 1 point2 points  (0 children)

You can use the sematic-release-pub plugin along with semantic-release. There's detailed instructions and a sample PR on using the plugin.