reactive-bulma 4.0.0 → 4.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +4 -6
  2. package/package.json +7 -7
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 having a problematic implementation, I decided to change version meaning for this project with the following:
196
- - Major versions (`1.0.0`, `2.0.0` and beyond) will refer to milestones/version achievement.
197
- - Minor versions (`1.1.0`, `1.2.0`, and so on) will refer to branch/story competition.
198
- - Patch versions (`1.0.1`, `1.0.2`, and so on) will refer to bug fixes only.
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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "reactive-bulma",
3
- "version": "4.0.0",
3
+ "version": "4.0.2",
4
4
  "description": "A component library based on React, Bulma, Typescript and Rollup",
5
5
  "keywords": [
6
6
  "typescript",
@@ -76,11 +76,11 @@
76
76
  "@storybook/react": "^7.6.12",
77
77
  "@storybook/react-webpack5": "^7.6.12",
78
78
  "@storybook/testing-library": "^0.2.2",
79
- "@testing-library/jest-dom": "^6.4.0",
80
- "@testing-library/react": "^14.2.0",
79
+ "@testing-library/jest-dom": "^6.4.1",
80
+ "@testing-library/react": "^14.2.1",
81
81
  "@testing-library/user-event": "^14.5.2",
82
- "@types/jest": "^29.5.11",
83
- "@types/react": "^18.2.48",
82
+ "@types/jest": "^29.5.12",
83
+ "@types/react": "^18.2.52",
84
84
  "@typescript-eslint/eslint-plugin": "^6.20.0",
85
85
  "@typescript-eslint/parser": "^6.20.0",
86
86
  "babel-jest": "^29.7.0",
@@ -89,14 +89,14 @@
89
89
  "eslint": "^8.56.0",
90
90
  "eslint-config-prettier": "^9.1.0",
91
91
  "eslint-plugin-react": "^7.33.2",
92
- "husky": "^9.0.7",
92
+ "husky": "^9.0.10",
93
93
  "hygen": "^6.2.11",
94
94
  "jest": "^29.7.0",
95
95
  "jest-environment-jsdom": "^29.7.0",
96
96
  "lint-staged": "^15.2.1",
97
97
  "npm-check-updates": "^16.14.14",
98
98
  "postcss": "^8.4.33",
99
- "prettier": "^3.2.4",
99
+ "prettier": "^3.2.5",
100
100
  "react": "^18.2.0",
101
101
  "react-dom": "^18.2.0",
102
102
  "rollup": "^4.9.6",