reactive-bulma 4.0.0 → 4.0.1
Sign up to get free protection for your applications and to get access to all the features.
- package/README.md +4 -6
- package/package.json +1 -1
package/README.md
CHANGED
@@ -192,15 +192,13 @@ In case you want to make your fork, I recommend you to update at least weekly us
|
|
192
192
|
|
193
193
|
## Versioning
|
194
194
|
|
195
|
-
After investigating [semantic-release documentation](https://semantic-release.gitbook.io/semantic-release/) (refer to [#3](https://github.com/NicolasOmar/reactive-bulma/issues/3)) and
|
196
|
-
- Major versions (`
|
197
|
-
- Minor versions (`
|
198
|
-
- Patch versions (`
|
195
|
+
After investigating [semantic-release documentation](https://semantic-release.gitbook.io/semantic-release/) (refer to [#3](https://github.com/NicolasOmar/reactive-bulma/issues/3)) and finishing the last version according to the original roadmap, I decided to give the following meaning to project's versions after `v4.0.0`:
|
196
|
+
- Major versions (`5.0.0`, `6.0.0` and beyond) will refer to milestones achievement and significant changes on existing components that will need extra attention before the update.
|
197
|
+
- Minor versions (`4.1.0`, `4.2.0`, and so on) will refer to new components or modifications of existing ones.
|
198
|
+
- Patch versions (`4.0.1`, `4.0.2`, and so on) will refer to bug fixes or weekly dependencies updates.
|
199
199
|
|
200
200
|
To check the current project's status, go to the [Roadmap](#roadmap) section.
|
201
201
|
|
202
|
-
In case you are interested in check current project's status, you can go to [Roadmap](#roadmap) section.
|
203
|
-
|
204
202
|
### Branching
|
205
203
|
|
206
204
|
Given the mentioned release logic, `main` is the only static branch, and each developed feature or fix will have a unique branch with its PR and a merge commit following [semantic versioning](https://semver.org/) and [semantic commits](https://github.com/semantic-release/semantic-release#commit-message-format) specifications.
|