package-sets icon indicating copy to clipboard operation
package-sets copied to clipboard

Automate Version Updates

Open andys8 opened this issue 5 years ago • 4 comments

I've noticed quite often the package set is missing a recent version of a library. Manually checking it out, adding it, opening a PR, and waiting for the release, feels like it could be automated.

Asking @f-f directly I learned already a lot. Summarized here:

First of all pursuit or pursuit-backups is not the source of truth regarding library versions. Github is.

There is script that automatically bumped versions to the latest. It recently broke and needs to be fixed or rewritten:

https://github.com/spacchetti/pacchettibotti/blob/master/src/PacchettiBotti/Threads/PackageSets.hs

There will be a new registry. Once the registry is in place would be much easier. It will be backwards compatible to package-sets.

Script

I think a basic script could look like this:

  • Checkout package-sets
  • For every package defined:
    • Look if there is a git tag with a newer version
    • Open question: What if dependencies changed?
    • If that's the case, create a pull request (if there is none already existing?)
    • CI on package-sets will check if the bump is okay

Related Issues

See also https://github.com/purescript/package-sets/issues/6

andys8 avatar Sep 20 '20 22:09 andys8