Now that #4217 has been merged, should release guide be updated to remove the instructions specifying that?

CI is failing because we build the package set to verify no breaking changes were introduced in a PR. Unfortunately, it means the metadata package causes the build to fail. I'm looking into it.

To fix CI, it looks like we need to make an empty commit in spacchetti/purescript-metadata and add a tag for it. Since that affects package sets, I'm not sure if that triggers anything else. @f-f Could you clarify what that will do?

I need one approval before I can merge this and make the next release.

Could you clarify what that will do?

@JordanMartinez the metadata package is a giant hack so that we can keep track of purs' version inside package sets. The reason why this hack exists is that we can't change package sets' format due to keeping compatibility with psc-package, and getting rid of this hack is one of the reasons why I'm restructuring Spago's config format.

I can cut a new release of that so you don't need to depend on a fork here in this PR

@f-f I'd appreciate the new release. Thanks!

@JordanMartinez done!

Thanks!

Can I get an approval here?

@JordanMartinez I'm almost done with #4233; would you mind delaying this until Friday so this has a chance to go in first? If not, I can try to work it in to a 0.14.7 release instead.

@thomashoneyman Fine by me! But if it's delayed beyond Friday, then I will release this (so long as I get an approval).

Just waiting on reviews at this point, but the PR is complete.

I've updated this PR to account for the purs publish PR (#4233). Once CI builds, this just needs an approval, and then I can release it.