Skip to content

Releases: MarkBind/markbind

v7.1.1

16 Apr 11:49

Choose a tag to compare

markbind-cli

User Facing Changes

Breaking Changes

Also give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

Custom Plugin File Extensions & Node.js Bump

Old feature that was made obsolete:
Previously, custom plugins written in .js files were always loaded implicitly as CommonJS (CJS) modules, preventing the use of modern ESM packages inside plugins.

Any replacement feature:
MarkBind now explicitly supports both CJS and ESM plugins. Plugin loading now relies on explicit file extensions (.cjs and .mjs) to safely mix module types. Additionally, the minimum required Node.js version is now v22.12.

How authors should modify their website to migrate:
1. Rename existing plugins: Rename any existing CommonJS custom plugin files from myPlugin.js to myPlugin.cjs to guarantee they are processed correctly.
2. Writing new plugins: Use .mjs for new ES Module plugins.
3. Update Node.js: Ensure your local environment and CI/CD deployment pipelines (e.g., GitHub Actions, Netlify) are using Node.js v22.12 or higher.


Features

Enhancements

Fixes

Documentation

Developer Facing Changes

Code Quality

DevOps Changes

Dependencies

Miscellaneous

Full Changelog: v6.3.1...v7.1.1

v7.1.0

16 Apr 11:25

Choose a tag to compare

markbind-cli

User Facing Changes

Breaking Changes

Also give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

Custom Plugin File Extensions & Node.js Bump

Old feature that was made obsolete:
Previously, custom plugins written in .js files were always loaded implicitly as CommonJS (CJS) modules, preventing the use of modern ESM packages inside plugins.

Any replacement feature:
MarkBind now explicitly supports both CJS and ESM plugins. Plugin loading now relies on explicit file extensions (.cjs and .mjs) to safely mix module types. Additionally, the minimum required Node.js version is now v22.12.

How authors should modify their website to migrate:
1. Rename existing plugins: Rename any existing CommonJS custom plugin files from myPlugin.js to myPlugin.cjs to guarantee they are processed correctly.
2. Writing new plugins: Use .mjs for new ES Module plugins.
3. Update Node.js: Ensure your local environment and CI/CD deployment pipelines (e.g., GitHub Actions, Netlify) are using Node.js v22.12 or higher.


Features

Enhancements

Fixes

Documentation

Developer Facing Changes

Code Quality

DevOps Changes

Dependencies

Miscellaneous

Full Changelog: v6.3.1...v7.1.0

v7.0.1

16 Apr 11:12

Choose a tag to compare

markbind-cli

User Facing Changes

Breaking Changes

Also give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

Custom Plugin File Extensions & Node.js Bump

Old feature that was made obsolete:
Previously, custom plugins written in .js files were always loaded implicitly as CommonJS (CJS) modules, preventing the use of modern ESM packages inside plugins.

Any replacement feature:
MarkBind now explicitly supports both CJS and ESM plugins. Plugin loading now relies on explicit file extensions (.cjs and .mjs) to safely mix module types. Additionally, the minimum required Node.js version is now v22.12.

How authors should modify their website to migrate:
1. Rename existing plugins: Rename any existing CommonJS custom plugin files from myPlugin.js to myPlugin.cjs to guarantee they are processed correctly.
2. Writing new plugins: Use .mjs for new ES Module plugins.
3. Update Node.js: Ensure your local environment and CI/CD deployment pipelines (e.g., GitHub Actions, Netlify) are using Node.js v22.12 or higher.


Features

Enhancements

Fixes

Documentation

Developer Facing Changes

Code Quality

DevOps Changes

Dependencies

Miscellaneous

Full Changelog: v6.3.1...v7.0.1

v7.0.0

06 Apr 06:00
8d5c8e7

Choose a tag to compare

v7.0.0 Pre-release
Pre-release

markbind-cli

User Facing Changes

Breaking Changes

Also give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

Custom Plugin File Extensions & Node.js Bump

Old feature that was made obsolete:
Previously, custom plugins written in .js files were always loaded implicitly as CommonJS (CJS) modules, preventing the use of modern ESM packages inside plugins.

Any replacement feature:
MarkBind now explicitly supports both CJS and ESM plugins. Plugin loading now relies on explicit file extensions (.cjs and .mjs) to safely mix module types. Additionally, the minimum required Node.js version is now v22.12.

How authors should modify their website to migrate:
1. Rename existing plugins: Rename any existing CommonJS custom plugin files from myPlugin.js to myPlugin.cjs to guarantee they are processed correctly.
2. Writing new plugins: Use .mjs for new ES Module plugins.
3. Update Node.js: Ensure your local environment and CI/CD deployment pipelines (e.g., GitHub Actions, Netlify) are using Node.js v22.12 or higher.


Features

Enhancements

Fixes

Documentation

Developer Facing Changes

Code Quality

DevOps Changes

Dependencies

Miscellaneous

Full Changelog: v6.3.1...v7.0.0

v6.3.1

25 Feb 19:03
e4a2c2e

Choose a tag to compare

markbind-cli

User Facing Changes

Fixes

  • Add additional npm run setup step in docs on Release by @gerteck in #2844
    • Fixes bug where version number did not reflect correctly in CLI.

Developer Facing Changes

Code Quality

  • Remove unused legacy code to avoid confusion by @gerteck in #2847

DevOps Changes

  • Add additional npm run setup step in docs on Release by @gerteck in #2844

Dependencies

Full Changelog: v6.3.0...v6.3.1

v6.3.0

25 Feb 16:09
4dda883

Choose a tag to compare

markbind-cli

What's Changed

User Facing Changes

Enhancements

Fixes

  • Fix markbind serve regression by @Harjun751 in #2837
  • Lock minimatch version to version before regression in WalkSync package by @gerteck in #2841

Documentation

Developer Facing Changes

Code Quality

Dependencies

  • Lock minimatch version to version before regression in WalkSync package by @gerteck in #2841

Full Changelog: v6.2.0...v6.3.0

v6.2.0

03 Feb 08:54
41b471d

Choose a tag to compare

markbind-cli

User Facing Changes

Features

Enhancements

Fixes

Documentation

  • Fix broken link to syntax guide in default template by @Harjun751 in #2799
  • Add example of content processing flow in developer documentation by @Harjun751 in #2777
  • Update architecture diagram to use mermaid by @yihao03 in #2788

Developer Facing Changes

Code Quality

  • Update ug-site.json by @gerteck in #2766
  • Upgrade lerna, jest and typescript by @gerteck in #2769
  • Cleanup gh-pages cache after deployment by @gerteck in #2773
  • Structurally refactor Site class into Facade and separate Managers by @gerteck in #2775
  • Remove bluebird dependency from async functions by @gerteck in #2803
  • Remove rewrap of promisify for gh-pages publish by @gerteck in #2806
  • Silence expected noisy console warnings in Cardstack by @gerteck in #2826
  • Update CLI log-cleaning function to preserve files if present by @Harjun751 in #2811
  • Add AGENTS.md files to provide guidelines for project and packages by @gerteck in #2814
  • Add update-docs skill by @Harjun751 in #2813

DevOps Changes

Dependencies

New Contributors

Full Changelog: v6.1.0...v6.2.0

v6.1.0

26 Dec 05:02
ae1bca2

Choose a tag to compare

markbind-cli

User Facing Changes

Features

  • Add support for generating other file extensions in MarkBind Sites by @gerteck in #2762

Documentation

  • Enable mermaid plugin for Developer Guide by @gerteck in #2759
  • Enhance documentation for Nunjucks variables by @gerteck in #2764

Developer Facing Changes

Full Changelog: v6.0.3...v6.1.0

v6.0.3

16 Dec 12:03
f2f52bd

Choose a tag to compare

markbind-cli

User Facing Changes

Fixes

Documentation

Developer Facing Changes

Code Quality

Full Changelog: v6.0.2...v6.0.3

v6.0.2

05 Jul 19:13

Choose a tag to compare

markbind-cli

User Facing Changes

Fixes

Developer Facing Changes

Code Quality

  • Gitignore page-vue-render.js files in CLI Functional Tests by @gerteck in #2718

Full Changelog: v6.0.1...v6.0.2