Package update service #1972
finestructure
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
I gotta admit, I was eyeing that structure the other day when I noticed a PR against the server that had various dependency updates and realized it had come from a system rather than an individual. It's a nice option to have to be able to "opt into", but it seems to be most compelling for server-side swift (and keeping track of that world) over anything more iOS or macOS specific. From my quick read of that code, it looks like it you stuff wouldn't compile on Linux, then it wouldn't be easy for the underlying GHA plugin to do it's work to update your iOS specific library - but I didn't look all that deeply into it. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Here's an idea that's not terribly unique but it could make a nice extension of SPI: an opt-in mechanism which does a package update refresh on repositories on a given cycle.
For instance, in SPI-server itself we use https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/blob/new-routing/.github/workflows/package-update.yml to update our dependencies every Monday.
We could add support for a new key in
.spi.yml
where authors opt-in and configure a frequency and we do the package update and open a PR against their repo automatically, without requiring any further setup.Beta Was this translation helpful? Give feedback.
All reactions