PARADIGM.MAJOR.MINORalthough all Masonite packages follow the SemVer versioning schema which is
MiraFramework/masoniterepository) contains only the basic file structure of the application. All of the core framework functionality is inside the
MasoniteFramework/corerepository which can be updated as much as every day or once per month.
MiraFramework/masonitedoes not require major updates, we can follow RomVer nicely and keep the versioning number artificially lower. Any major updates to this repsository will likely just be file structure changes which should rarely happen unless there are major architectural changes.
MasoniteFramework/corerepositories are released on Github, Travis CI will run tests and automatically deploy to PyPi. These major version numbers should correspond to the version of Masonite they support. For example, if the
MasoniteFramework/masonitereleases to version 1.4,
MasoniteFramework/coreshould bump up to 1.4.x regardless of changes.
MasoniteFramework/masonitedoes not have a corresponding PyPi package and is only for installing new Masonite projects. See the
craft newcommand under The Craft Command documentation. The
craft newcommand will download a zip of the latest release of Masonite, unzip it and rename the folder. Once the next release for this repository is ready, it will be released but marked as a
Pre-releaseand therefore will not be installable by the default
craft new project_name --version 1.6and installing that version of Masonite.