When there is a new version of Alpine, PHP, extension or package, you can contribute by either sending a PR that packages the pkgver= on the given package, or comment on this topic, listing the update.
TODO:
Create an issue template for package update reporting.
Long version:
Hello everyone, is a really painful job to keep additional packages/extensions up-to-date.
If anyone have some spare time, please, send PR's bumping the pkgver=x.x.x variable on the packages.
I'll try to get all of those updated this week, and eventually build a script to bump those automatically, but for now, PR's are very much welcomed.
@xarem I think on a conversation long ago, you mentioned having a script for this right? If that's the case, let me know what are you doing so we can collaborate on making this true.
I was also thinking about making a PR bot with newer PECL versions, maybe would be nice, since this repo is completely being built on GitHub actions right now.
TL;DR;
When there is a new version of Alpine, PHP, extension or package, you can contribute by either sending a PR that packages the
pkgver=on the given package, or comment on this topic, listing the update.TODO:
Create an issue template for package update reporting.
Long version:
Hello everyone, is a really painful job to keep additional packages/extensions up-to-date.
If anyone have some spare time, please, send PR's bumping the
pkgver=x.x.xvariable on the packages.I'll try to get all of those updated this week, and eventually build a script to bump those automatically, but for now, PR's are very much welcomed.
@xarem I think on a conversation long ago, you mentioned having a script for this right? If that's the case, let me know what are you doing so we can collaborate on making this true.
I was also thinking about making a PR bot with newer PECL versions, maybe would be nice, since this repo is completely being built on GitHub actions right now.