Versioning Policy

PureScript can be perceived from two different perspectives:

1. PureScript-the-application (e.g. using purs to compile code)
2. PureScript-the-library (e.g. building a tool that depends on the purescript package)

This project is versioned using SemVer 2.0.0, not PVP because users of PureScript-the-application are the intended audience. Thus, breaking changes to PureScript-the-application are reflected in this project's version. Since CoreFn is considered part of PureScript-the-application, a breaking change to that format is reflected in the project version.

Since PureScript-the-library is used by internal tools like Try PureScript and Pursuit, it must be published to Hackage as a library. However, PureScript-the-library is considered unstable and can make breaking changes to library users without reflecting that in the version.