Skip to content

Latest commit

 

History

History
62 lines (34 loc) · 2.51 KB

File metadata and controls

62 lines (34 loc) · 2.51 KB

Changelog

4.1.0 (September 16, 2025)

Features

  • Introduced --config CLI parameter which allows providing custom configuration filename that will be used instead of the default mrgit.json file. Closes #189.

4.0.0 (June 26, 2025)

BREAKING CHANGES

  • Updated the required version of Node.js to 22 after bumping all @ckeditor/ckeditor5-dev-* packages to the latest ^50.0.0 version.

Bug fixes

  • The mrgit status command should not print an error when processing a repository without tags or with a partially cloned history that causes tags to be assigned to non-existing commits. Closes #179.

3.0.0 (2025-03-14)

BREAKING CHANGES

  • Upgraded the minimal version of Node.js to 20.0.0 due to the end of LTS.

Other changes

  • Updated the required version of Node.js to 20. (commit)

2.1.0 (2023-08-28)

Features

  • Added support for executing commands in the root repository. Closes #160. (commit)

    Add the $rootRepository option to the mrgit.json configuration file to enable this feature. Its value should be a repository GitHub identifier (the same as defining the dependencies values). You can also define the option within the preset feature.

    Below, you can find a list of supported commands that take into consideration the root repository if specified:

    • checkout
    • commit
    • diff
    • exec
    • fetch
    • pull
    • push
    • status
    • sync

    To disable executing a command in the root repository without modifying the configuration file, you can add the --skip-root modifier to mrgit. Example: mrgit status --skip-root.

2.0.3 (2023-06-05)

Internal changes only (updated dependencies, documentation, etc.).


To see all releases, visit the release page.