digitalMoksha

@kivikakk ouch. This is a huge breaking change for us. We've built significant functionality on top of inline sourcepos. Its removal is a real problem for us. I understand it's...

Thanks @kivikakk 🙇. I agree with naming an option `experimental-inline-sourcepos`. I'm not happy with "garbage in, garbage out" either. So far we haven't hit these particular cases, but as we...

To better clarify what we use it for, in GitLab we have a rich text editor for our markdown fields (comments, descriptions, etc). Markdown is the single source of truth,...

Yeah, it's very much [a work in progress](https://gitlab.com/groups/gitlab-org/-/epics/7722) 😅 Though I am going to have to go back and adjust expectations.

Possibly, though I don't understand the ramifications of that yet, particularly since at the moment it's the generated HTML that gets converted into the editor. > the big change forewarned...

@yannham I'm curious, based on https://github.com/kivikakk/comrak/issues/371 it looks like you're building the AST programmatically. Are you still using 0.17, or did you get the latest working?

In particular it looks like a PR from a fork doesn't have the correct permissions. https://github.com/mshick/add-pr-comment/issues/67 and https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

> Extensions for me...mean extending the syntax of markdown with custom things. E.g., JSX, math with dollars, etc. > > The first is as far as I understand impossible in...

Nice!!

The way I've handled it in a project is by using a release PR. You create a PR that bumps the version number. On merging with `main`, CI checks if...