Conversation
- @native-html/css-processor@2.0.0 - @native-html/render@1.0.0 - @native-html/transient-render-engine@12.0.0
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #30 +/- ##
=======================================
Coverage 98.65% 98.65%
=======================================
Files 140 140
Lines 2076 2076
Branches 633 637 +4
=======================================
Hits 2048 2048
Misses 27 27
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
- @native-html/render@1.0.1
- @native-html/render@1.0.2
|
@jsamr may I ask you again for the deprecation of |
|
@5ZYSZ3K I'm a bit underwater, but will try to at least do it at the NPM and README level after this one is released. |
| { | ||
| "name": "@native-html/render", | ||
| "version": "1.0.0-alpha.0", | ||
| "version": "1.0.2", |
There was a problem hiding this comment.
Could we continue the versioning scheme of react-native-render-html to highlight continuity?
If breaking changes were introduced (likely since we likely don't support older RN versions), v7, if not, iterate on v6.x
There was a problem hiding this comment.
I think that since we decided to give it a new name, it would make sense to start from 1.0.0
However, I should add a note about that to the README.md, and I will do that now
There was a problem hiding this comment.
since we decided to give it a new name, it would make sense to start from 1.0.0
I disagree. It is the same library, with a different name to highlight a transfer of ownership. Everyone will wonder if this version is in the continuity of RNRH v6. If it is, let's keep v6.x to make that clear.
There was a problem hiding this comment.
Okay, I get that
The next release will be 7.0.0
I have to update the docs anyway
2 participants
Release of
@native-html/render1.0.0 (actually 1.0.2, I made two mistakes during the release)