Dendron 0.65 has sprouted 🌱

This week features tons of bug fixes, an easier to use schema format, and a new command to move headers within notes to different notes!

Note that there are some automatic configuration changes that we are making as part of our config consolidation. This should happen transparently but if for some reason your dendron.yml is not migrated, you can follow instructions 0.65 to manually upgrade your config.


  • enhance(schemas): expand schema format to allow for inlined children (docs)
  • feat(command): move header command (docs)
  • enhance(cli): support output option when using dendron note lookup (docs (Private))


This release includes various fixes, and a breaking changes section about new dendron.yml changes. This should automatically be taken care of when starting up your Dendron workspace. For more information, see the changelog. Another way to migrate to the latest configuration format is via the latest CLI release:

dendron dev run_migration --migrationVersion 0.64.1

Everything Else

  • enhance(cli): add run migration command in cli (docs (Private))
  • enhance(commands): update default aliases when note is updated
  • enhance(pods): enhance gdoc import formatting
  • fix(publish): make assetPrefix apply to all link elements
  • fix(workspace): update yml validation to latest config version
  • fix(publish): make 11ty publishing compatible with config version 3
  • fix(workspace): notes getting whitespace changes after workspace sync
  • fix(workspace): frontmatter variable substitution not rendering in preview V2
  • fix(markdown): email parsed as user tag & option to disable user tags and hashtags
  • fix(markdown): footnote links move view in publishing & preview
  • fix(publish): remove .next dir if it exists in publish init
  • fix(publish): title parts duplicated in Next.js publishing search
  • fix(commands): move header command modifying unrelated note content


Dendron Reading Series

This week's entry in the Dendron Reading Series.

Plain text is amazing becomes it is universally accessible but opponents argue that users are trading off nice UI and avanced functionality when using text based systems. But this is a false dichotomy and tools like Magit are a great example of the opposite, a text based interface that has nice form and function.

Thank You's

A big thanks to the following gardeners that brought up issues, contributions, and fixes to this release :man_farmer: :woman_farmer: You can see an overview of all roles here


Start anchor 065 not found