Automated port pr publishing

[mathisloge]

So i was wondering if there could be some automated way to publish ports directly from a github action

This would significantly minimize the effort for library maintainers if an action could be run on each release that would automatically open a PR in vcpkg and adjust the appropriate versions, etc.

It would be best if there was a pre-built action for this. The target repository should be customizable to also include private registiries

[AugP]

This is a really interesting suggestion and I am curious where we can take it. I'll tag our engineering team to share their thoughts on the feasibility.

[mathisloge]

@AugP is there some progress on this?

I've some real world projects which are wondering, why there isn't a automated workflow, for at least normal updating.

Dobiasd/frugally-deep#277 (comment)
commschamp/comms#1 (comment)

[Dobiasd]

To give some additional motivation, JFrog ConanCenter does this, and this is a much more pleasant experience from the point of view of a library maintainer. 😉

[autoantwort]

I think creating a GithubAction for that is not so hard, but you need a personal access token to create the PR in the GithubAction

[Dobiasd]

Ah, sorry. I think I meant conda-forge.

With all the C++-package managers, that one "needs" to support, I sometimes forget which ones I need to do something with and which ones I do not, when publishing a new version of one of my two main libraries (FunctionalPlus and frugally-deep).

Writing all steps down for all package managers also does not help that much in my case, because I don't release that often, and after a year or so, it's well possible that too many things already have changed. "Publishing" really is the main pain point for me in maintaining my libraries over the years. 🥴

And thus, it would be really awesome if all package managers could automatically "pull" the latest versions instead of me needing to manually "push" every time. 🙏

[Dobiasd]

I think creating a GithubAction for that is not so hard, but you need a personal access token to create the PR in the GithubAction

Yeah, makes sense. 👍
But why repeat that effort number_of_library times (i.e., in each lib), instead of solving it only once (i.e., in the package manager)?

[autoantwort]

I think this is the goal. There is also microsoft/vcpkg-tool#717 (comment).
But this still needs manual maintenance (for example when a lib needs a new dependency).

[Dobiasd]

I think this is the goal.

Nice, looking forward to it! 🚀

But this still needs manual maintenance (for example when a lib needs a new dependency).

Yeah, that's reasonable, I think. 👍