spago upgrade should use a compatible compiler version if no sets for the current one are available

[peterbecich]

The latest package set 50.1.1 https://github.com/purescript/registry/blob/main/package-sets/50.1.1.json
specifies PureScript 0.15.14.

Can that be updated to solve this error from spago upgrade?

❌ No package set found for the current compiler version.

Thanks

[f-f]

If you have purs@0.X.Y you can use any package set made for purs@0.X.Z, if Y >= Z.
So purs@0.15.15 can use any package set made for any purs 0.15.X.

FWIW, you can see which is the latest package set for each version:

spago registry package-sets --latest
+---------+------------+----------+
| VERSION | DATE       | COMPILER |
+---------+------------+----------+
| 10.0.0  | 2023-01-05 | 0.15.4   |
| 20.0.3  | 2023-04-08 | 0.15.7   |
| 27.2.0  | 2023-06-17 | 0.15.8   |
| 29.1.0  | 2023-07-18 | 0.15.9   |
| 43.3.0  | 2023-10-23 | 0.15.10  |
| 46.2.0  | 2023-11-23 | 0.15.12  |
| 47.10.0 | 2023-12-28 | 0.15.13  |
| 50.1.1  | 2024-02-23 | 0.15.14  |
+---------+------------+----------+

So the issue here is that spago upgrade should use any of these, as long as they are higher than your current version.

It should also allow you to specify a set to use with the --package-set flag, just like spago init does.

[thomashoneyman]

This seems it should be transferred to spago’s repo, as no dev happens here

[peterbecich]

Would someone transfer this? I don't have the ability; "Transfer issue" should be at the right side: https://docs.github.com/en/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository
Happy to create a new issue at https://github.com/purescript/spago of course

[f-f]

Oh sorry, I was entirely convinced it was in spago in the first place. I moved it now.