feat(#37): support spago@next -> the latest and unstable are both spago@next version, BREAKING CHANGE

[srghma]

#37

depends on purescript-contrib/purescript-github-actions-toolkit#20

[srghma]

hi @thomashoneyman
I have implemented as You suggested

[jamesdbrock]

I just ran the workflow and it passes. This PR looks good to me.

[thomashoneyman]

@jamesdbrock I’d like to wait to merge this until we can point at the non-forked GitHub actions toolkit library

[thomashoneyman]

This can now be updated to https://github.com/purescript-contrib/purescript-github-actions-toolkit/releases/tag/v0.6.0 (cc: @srghma)

[thomashoneyman]

We're only using a devshell so we should remove this packages section.

[srghma]

noticed too

commented out and

 ~/projects/setup-purescript   main  nix shell
warning: Git tree '/home/srghma/projects/setup-purescript' is dirty
error: flake 'git+file:///home/srghma/projects/setup-purescript' does not provide attribute 'packages.x86_64-linux.default' or 'defaultPackage.x86_64-linux'
 ✘  ~/projects/setup-purescript   main ±  nix shell #.devShells
warning: Git tree '/home/srghma/projects/setup-purescript' is dirty
error: flake 'git+file:///home/srghma/projects/setup-purescript' does not provide attribute 'packages.x86_64-linux.default' or 'defaultPackage.x86_64-linux'

[thomashoneyman]

@srghma other than my two minor comments this looks good to me and I can approve & merge. However, looks like the Windows CI is failing; not sure why it's failing the formatter check and I don't have any experience with Windows myself. Maybe @JordanMartinez or @f-f have seen something like this before?

[f-f]

Not sure I encountered exactly this before, but I wonder if this is due to the git line endings - in Spago's CI we have this snippet before the actions/checkout step:

    steps:
      # We set LF endings so that the Windows environment is consistent with the rest
      # See here for context: https://github.com/actions/checkout/issues/135
      - name: Set git to use LF
        run: |
          git config --global core.autocrlf false
          git config --global core.eol lf
          git config --global core.longpaths true

[thomashoneyman]

We can also just not do the formatting check on windows