Please, publish releases, not only tags

[hurricup]

It is hard to watch for library changes without it. GH notifies about releases, not tags.

[Leont]

We publish releases to CPAN

[hurricup]

Yes I know that.
But it is really comfortable to follow projects releases in one place. and it is not a big deal to draft release. Not necessary to attach archive there, it is more like a flag that specific tag is a release, not just some dev tag.
I'm not even sure if CPAN may notify about new releases.

[demerphq]

Maybe you should provide a link to docs on this, I have no idea what you are on about. Generally every tag we have in this repo is about a release, it would be unusual/unheard of for a comitter to push a tag for any other reason.

[hurricup]

Sure: https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases

[hurricup]

Looks like this: https://github.com/Camelcade/Perl5-IDEA/releases

[hurricup]

Or this (this more like perfect releases): https://github.com/shogo82148/actions-setup-perl/releases

[karenetheridge]

If someone has a Github Action that will create a release when a tag is pushed, I'll apply it to all my repos.

[Leont]

If someone has a Github Action that will create a release when a tag is pushed, I'll apply it to all my repos.

I think the resulting tarball is only workable if the repository matches the repo 1-on-1. This isn't even the case for this repository at the moment (the META files aren't committed), and it's very much not true for your typical repositories.

[hurricup]

I'm not quite sure that someone will really need to have binaries in the release when we have CPAN. This may be useful for artifacts with windows binaries, for example, when we have only not widely used chocolatey. I personally using msys2 binaries this way to configure CI.
For perl distributions it would be nice just to have releases to be able to get notified on updates.

I didn't use this myself, but seems there is an action for this: https://github.com/marketplace/actions/github-create-tag-release

[karenetheridge]

I suppose if we want the "github release" to match the actual tarball that we uploaded to PAUSE, then we'd need to do this as a post-release action -- such as in a dzil plugin. I'll happily add such a plugin to Dist-Zilla-Plugin-GitHub.

[Leont]

I suppose if we want the "github release" to match the actual tarball that we uploaded to PAUSE, then we'd need to do this as a post-release action -- such as in a dzil plugin. I'll happily add such a plugin to Dist-Zilla-Plugin-GitHub.

Yeah, I think that'd be a more sensible approach.

[zmughal]

For a private non-CPAN dist, I have the following in my dist.ini:

[FakeRelease]

[Run::AfterRelease / GitHubUpload ]
run = gh release create v%v %a

This requires an authenticated gh CLI.