Icons, fonts, colors, components and all user interface items for OSRD project.
Development will leverage preconstruct. Documentation yet to come.
In a nutshell: we consider our version numbers metadata of the project. We use Semantic Versioning.
We do not change the version on local package versions, we keep the file to the version 0.0.1-dev which is not a real version and can be easily identified as a development version.
The version numbers for our releases are solely managed through git tags. It implies that when we update a single package, we release all the project together : even if there are no changes between two release (let's say we update ui-icons but nothing else, we would make a release that would publish all packages anyway).
It's the tradeoff we make to keep the project simple and easy to manage, and to avoid the complexity of managing multiple compatible versions of the project.
In summary : we consider a version number as being an indivisible release of all the subpackages of the repository.
- Create a annotated git tag (let's say
0.0.30, you would do agit tag -a 0.0.30) on thedevbranch and push it. Note: we do not tag with a V in front of the version number, on our example the tag would be 0.0.30 and not v0.0.30. - Create a github release (By convention, we use the same name as the tag with the letter
vin front of it,v0.0.30. You can give fancy names to release if you want to :0.0.30 : Camembert, it will only appear in the release page of GitHub).
Create a folder and follow the structure of other packages (refer to the Development section for more information).
The package will be picked up automatically as long as it is included in the workspaces of the package.json file at the root of the project and that a section is added to the package.json in the package itself:
{
// ...
"publishConfig": {
"access": "public"
},
// ...
}If this section is not added, the package will not be published. Having a "private": true in the package.json will also prevent the package from being published.