Releases: rasendubi/uniorg
uniorg@1.2.0
Minor Changes
-
#109
dbf6452
Thanks @rasendubi! - Supportexport-snippet
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.export-snippet
has the following form:@@backend:value@@
. Example:@@html:<b>@@some text@@html:</b>
.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
-
#111
b45baf9
Thanks @rasendubi! - Supportline-break
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
uniorg-stringify@1.3.0
Minor Changes
-
#109
dbf6452
Thanks @rasendubi! - Supportexport-snippet
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.export-snippet
has the following form:@@backend:value@@
. Example:@@html:<b>@@some text@@html:</b>
.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
-
#111
b45baf9
Thanks @rasendubi! - Supportline-break
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
uniorg-rehype@1.2.0
Minor Changes
-
#109
dbf6452
Thanks @rasendubi! - Supportexport-snippet
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.export-snippet
has the following form:@@backend:value@@
. Example:@@html:<b>@@some text@@html:</b>
.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
-
#111
b45baf9
Thanks @rasendubi! - Supportline-break
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
uniorg-parse@3.0.1
Patch Changes
- #112
0e1d4b7
Thanks @rasendubi! - Allow Zero-Width Space as emphasis separator.
uniorg-parse@3.0.0
Major Changes
-
#109
dbf6452
Thanks @rasendubi! - Supportexport-snippet
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.export-snippet
has the following form:@@backend:value@@
. Example:@@html:<b>@@some text@@html:</b>
.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
-
#111
b45baf9
Thanks @rasendubi! - Supportline-break
in uniorg, uniorg-parse, uniorg-rehype, and uniorg-stringify.This is a breaking change for uniorg-parse as it may output nodes unknown to downstream users (uniorg-rehype and uniorg-stringify). If you upgrade uniorg-parse, you should also upgrade uniorg-rehype and uniorg-stringify to the corresponding versions.
rollup-plugin-orgx@1.0.3
Patch Changes
- Updated dependencies []:
- @uniorgjs/orgx@1.0.7
rollup-plugin-orgx@1.0.2
Patch Changes
- Updated dependencies []:
- @uniorgjs/orgx@1.0.6