How To Create "@be" (Bleeding Edge) Module Releases

Communities FORGEBOX
1

I’m working updates to one of my open source Forgebox modules and I’d like to test out my changes on a real app before bumping the version and publishing to forgebox.

What’s the Ortus convention for prepping a project and publishing the development branch of a repo so that it can be installed as @be?

For reference, when I create a new stable release, these are the steps I take:

  1. Make sure tests for all supported engines pass green
  2. Create a new release branch (e.g. 2.0.0)
  3. Update readme, changelog, and box.json with the version number
// box.json
{
  "name": "mymodule",
  "slug": "mymodule",
  "version": "2.0.0", // <- bumped up from 1.0.0
  "location":"ForgeboxStorage",
}
  1. In Commandbox, forgebox publish (or forgebox publish --force if I screw something up)

I would love some official guidance on the best way to handle publishing (or making available) unstable pre-release versions.