Update to 0.15.15 & latest package set

[pete-murphy]

Changes

• Bump PureScript compiler from 0.15.13 to 0.15.15
• Update package set from psc-0.15.13-20231219 to psc-0.15.15-20260506
• Regenerate stack.yaml.lock
• Update client/src/Try/SharedConfig.purs via npm run updateConfigVersions
• Update changelog

Notes

3 packages were excluded from the package set due to broken git repos/tags:

• record-extra-srghma — tag v0.2.8 doesn't exist
• url-regex-safe — repo not found
• yoga-postgres — tag v6.0.0 doesn't exist

[pete-murphy]

There's a note in RELEASE.md

The try.purescript.org server only has a limited amount of memory. If the package set we use in deployment is too large, the server will run out of memory.

Before deploying an updated package set, someone (your reviewer) should check that the memory required to hold the package set's externs files does not exceed that of the try.purescript.org server.

Is there a simple way to confirm this is within limits? Does this line in the start script mean that 3GB is the max?

Here's size of externs.cbor before these changes

$ find staging/output -name 'externs.cbor' | wc -l
3946
$ find staging/output -name 'externs.cbor' -exec du -ch {} + | tail -1
184M   total

and after

$ find staging/output -name 'externs.cbor' | wc -l
7847
$ find staging/output -name 'externs.cbor' -exec du -ch {} + | tail -1
327M    total

[thomashoneyman]

It's been long enough I can't quite remember the details 😆 in the absence of better information, I'd be happy merging and reverting in the case the server isn't healthy.

[pete-murphy]

@thomashoneyman I am closing this in favor of #316 which also updates to latest Spago. But I think that can't be merged as-is, I do indeed seem to be hitting the memory limit: #316 (comment)