@vanelsas/baredom 2.0.0 → 2.0.1
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.
- package/CHANGELOG.md +7 -0
- package/README.md +3 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,13 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to BareDOM will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [2.0.1] - 2026-04-10
|
|
6
|
+
|
|
7
|
+
### Fixed
|
|
8
|
+
|
|
9
|
+
- Release pipeline: version references in build.clj, deps.edn, and pom.xml now match package.json (were stuck at 1.4.0/1.2.0, causing Clojars deploy to fail for 2.0.0)
|
|
10
|
+
- CI workflow: npm publish step now uses continue-on-error to avoid blocking Clojars deploy
|
|
11
|
+
|
|
5
12
|
## [2.0.0] - 2026-04-10
|
|
6
13
|
|
|
7
14
|
### Added
|
package/README.md
CHANGED
|
@@ -116,13 +116,13 @@ BareDOM can be consumed three ways: as a **ClojureScript source dependency** (Cl
|
|
|
116
116
|
Add BareDOM to your `deps.edn`:
|
|
117
117
|
|
|
118
118
|
```clojure
|
|
119
|
-
{:deps {com.github.avanelsas/baredom {:mvn/version "2.0.
|
|
119
|
+
{:deps {com.github.avanelsas/baredom {:mvn/version "2.0.1"}}}
|
|
120
120
|
```
|
|
121
121
|
|
|
122
122
|
Or in your `shadow-cljs.edn` dependencies:
|
|
123
123
|
|
|
124
124
|
```clojure
|
|
125
|
-
:dependencies [[com.github.avanelsas/baredom "2.0.
|
|
125
|
+
:dependencies [[com.github.avanelsas/baredom "2.0.1"]]
|
|
126
126
|
```
|
|
127
127
|
|
|
128
128
|
Then require component namespaces directly and call their `init!` function once at startup:
|
|
@@ -179,7 +179,7 @@ Add the npm package to your `package.json`:
|
|
|
179
179
|
```json
|
|
180
180
|
{
|
|
181
181
|
"dependencies": {
|
|
182
|
-
"@vanelsas/baredom": "^2.0.
|
|
182
|
+
"@vanelsas/baredom": "^2.0.1"
|
|
183
183
|
}
|
|
184
184
|
}
|
|
185
185
|
```
|