@sveltia/cms 0.120.0 → 0.120.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/README.md CHANGED
@@ -127,15 +127,19 @@ Due to its unfortunate abandonment in early 2022, Netlify CMS spawned 3 successo
127
127
  - **Sveltia CMS**: not a fork but a **complete rewrite**
128
128
  - Started in November 2022, first appeared on GitHub in March 2023
129
129
  - ✅ Actively developed with frequent releases and numerous improvements
130
- - ✅ Solved more than 270 issues reported in the Netlify/Decap CMS repository
130
+ - ✅ Relevant issues are actively being addressed regardless of their age or status
131
+ - ✅ Most of bug reports are addressed promptly, usually within a day
132
+ - ✅ No known unpatched security vulnerabilities, with dependencies kept up-to-date
131
133
  - [Decap CMS](https://github.com/decaporg/decap-cms): a rebranded version
132
134
  - [Announced in February 2023](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/) as an official continuation with a Netlify agency partner taking ownership
133
135
  - ⚠️ Mostly low activity with only occasional releases and a few minor improvements
134
- - A moderate severity [XSS vulnerability](https://github.com/advisories/GHSA-xp8g-32qh-mv28), high severity dependency vulnerabilities, fatal crashes and many other bugs remain unaddressed
136
+ - ⚠️ Seemingly random issues were closed as stale following the rebranding
137
+ - ⚠️ Bug reports continue to pile up, often without any response
138
+ - ❌ A moderate severity [XSS vulnerability](https://github.com/advisories/GHSA-xp8g-32qh-mv28), high severity dependency vulnerabilities and fatal crashes remain unaddressed
135
139
 
136
140
  Sveltia CMS is the only project that doesn’t inherit the complexity, technical debt, and numerous bugs of Netlify CMS, which was launched in 2015. Our product is **better by design**:
137
141
 
138
- - We have rebuilt the app from scratch using a [modern framework](https://svelte.dev/)
142
+ - We rebuilt the app from scratch using a [modern framework](https://svelte.dev/)
139
143
  - We don’t reuse any part of the predecessor’s codebase
140
144
  - We incorporate i18n support into the core instead of adding it as an afterthought
141
145
  - We closely monitor and analyze the predecessor’s issue tracker
@@ -175,7 +179,8 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
175
179
  - or every single issue that’s relevant, fixable, and worth dealing with 🔥
176
180
  - Issues include everything:
177
181
  - Outstanding issues from feature requests to bug reports
178
- - [Issues closed as stale](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+%22Closing+as+stale%22) or without an effective solution
182
+ - [Issues closed as stale](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+%22Closing+as+stale%22)
183
+ - Issues closed without an optimal solution
179
184
  - [Discussions](https://github.com/decaporg/decap-cms/discussions)
180
185
  - Stalled [pull requests](https://github.com/decaporg/decap-cms/pulls)
181
186
  - Many of the bugs, including the annoying crashes, have already been solved