As soon as this gets merged, releases will work as follows:
PR merges will be collected by release-please into a release PR. The team at Supabase decides when a release is ready to go out, usually weekly or bi-weekly.
Every PR merge (that uses feat: or fix: titles) will result in a release candidate release with tag rc<version>. Example: if the new release will be 2.140.0 then the RC release will be rc2.140-rc.1, and so on.
Once the release PR is merged, an official release will be published with the tag v<version>, or per the example v2.140.0.
Releases with a patch version of 0 get a special branch release/v2.140.0 which can be used to patch that and only that major+minor version, using the same process as above.
RC releases are tagged rc in NPM and regular ones as latest. Patched releases get the label patched.
Adds a new release process based on release-please.
As soon as this gets merged, releases will work as follows:
feat:orfix:titles) will result in a release candidate release with tagrc<version>. Example: if the new release will be2.140.0then the RC release will berc2.140-rc.1, and so on.v<version>, or per the examplev2.140.0.0get a special branchrelease/v2.140.0which can be used to patch that and only that major+minor version, using the same process as above.rcin NPM and regular ones aslatest. Patched releases get the labelpatched.Similar to: