Skip to content

Releases: rasendubi/uniorg

[email protected]

19 May 01:15
2b8e9ca
Compare
Choose a tag to compare

Minor Changes

  • #109 dbf6452 Thanks @rasendubi! - Support export-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! - Support line-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.

[email protected]

19 May 01:15
2b8e9ca
Compare
Choose a tag to compare

Minor Changes

  • #109 dbf6452 Thanks @rasendubi! - Support export-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! - Support line-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.

[email protected]

19 May 01:15
2b8e9ca
Compare
Choose a tag to compare

Minor Changes

  • #109 dbf6452 Thanks @rasendubi! - Support export-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! - Support line-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.

[email protected]

19 May 08:50
6f60a49
Compare
Choose a tag to compare

Patch Changes

[email protected]

19 May 01:15
2b8e9ca
Compare
Choose a tag to compare

Major Changes

  • #109 dbf6452 Thanks @rasendubi! - Support export-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! - Support line-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.

[email protected]

19 May 08:50
6f60a49
Compare
Choose a tag to compare

Patch Changes

[email protected]

19 May 01:15
2b8e9ca
Compare
Choose a tag to compare

Patch Changes

[email protected]

19 May 01:14
2b8e9ca
Compare
Choose a tag to compare

[email protected]

19 May 01:14
2b8e9ca
Compare
Choose a tag to compare

[email protected]

19 May 01:14
2b8e9ca
Compare
Choose a tag to compare