I think this ought to use a tag from some kind of configuration rather than hardcoding the branch name, so that we can change these without breaking the currently released version. In practice we will want this to be the tag from the current version.

Yea — I could thread this in as an argument to main, so that it can be accessed in various places taken from outside the PureScript code.

Sounds good 👍

I could also do that with the entire dev / prod configurations in that case — thoughts?

If that makes the overall setup simpler, sure, I don't see why not.

On second thought, doing this would require some kind of text replacement processing pass to work. After all, this example is code loaded literally into the Try PureScript editor.

Otherwise, we'd have to do something like read the current tag from data in the index.html file or something like that, but this would be user-visible code and I'm not a huge fan of that.

Another option is to manually hard-code the tag as part of the release process and document where the tag would need to be updated -- we release so infrequently that this feels legitimately like an option.

True - I think manually hardcoding the tag and documenting that it needs updating will work.

Perhaps we should split the repository README so that the main README is for users and there's a separate development guide. It could include instructions for developing, like we already have, but could also have a release guide which includes:

• Updating the hardcoded tag
• Checking externs sizes
• Running the deployment

What do you think?

For now I've just added a note about the hardcoded tags to the README, but I think we probably do want a dedicated, separate development + release guide.