Skip to content
Branch: master
Find file Copy path
Find file Copy path
1 contributor

Users who have contributed to this file

194 lines (131 sloc) 7 KB


All notable changes to this project are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning. The file is auto-generated using Conventional Commits.



nothing new to show for… yet!

0.1.1The Quick Fix


What goes up, must come down.

This release fixes several issues that came to light after releasing v0.1.0, which put the repository in a state with no unreleased changes, triggering branching logic that still had a few bugs 🐛.

Those bugs are no more.

Still, this is a perfect reminder to start working on those unit tests.


This release is made possible by the following people (in alphabetical order). Thank you all for your contributions. Your work – no matter how significant – is greatly appreciated by the community. 💖


Bug Fixes

  • prevent subtraction with overflow (2e383d1)

    Return early if there are no commits to take from the stack.

  • correctly check for no new changes (61ceeed)

    Since unreleased is an object, it never reports back as being falsy, so we instead check for an empty list of changes in the object.

0.1.0Ship It!


The first release of Jilu 🎉.

Jilu is a tool that generate a change log for you, based on the state of your Git repository. It converts conventional commits into a human readable change log, using Git tags to annotate your releases with titles, release notes and more. You can tweak your change log to suit the needs of your community and even integrate the jilu binary into your CI workflow for automated updates.

This release is an example of using an annotated Git tag to attach a custom release title (in this case "Ship It!") and a hand-written release note (this message) to a release. This makes it more pleasant for your readers to get up-to-date on what has changed, while also providing them with an accurate list of all the relevant changes part of the release (which for this project means all commits with the types "feat", "fix" or "perf").

Since the notes are inlined into the change log, you can use markdown and have it render as expected. Don't go too crazy with this though, as people might not always read your tag annotations from a client that can render Markdown text to HTML. And while that is the exact purpose of markdown (being easy to read in non-rendered form), you can still get too carried away, making your notes less readable than they could be.

You can also embed images to give more visual appeal to your release notes, as a picture is worth a thousand words when you want to let your audience know about all those amazing new features.

Release Notes

Now first I'm going to automatically (really! 🙈) thank myself for my contributions (there will be a feature to exclude certain core contributors from getting thanked all the time), and then I invite you to go read the changes below, and hopefully you find any use for this tool, as I have.

Be sure to check out the project README if you haven't already!


This release is made possible by the following people (in alphabetical order). Thank you all for your contributions. Your work – no matter how significant – is greatly appreciated by the community. 💖



  • show commit type of unreleased changes (10a3e99)

    The goal is to keep the list of unreleased changes more succinct, but still provide enough information to see the most important upcoming changes at a glance.

    With this change, the commit type is added to the single-line description of each change, giving better insight into how relevant each change is.

    When breaking changes are added to the change log, that too should somehow be conveyed in the upcoming changes list, so people can anticipate these breaking changes by reading the change log.

  • configurable change log template and config (d462839)

    It's now possible to alter the way your change log looks by combining a set of configuration settings and an optional custom template system.

    The eventual goal is to support both use cases of making simple changes to the default template to suit your needs by using configuration settings, or to style your change log from scratch using your own template.

    Template support is fully supported with this change, and the first set of configuration settings are also added. More will follow in the future.

  • initial working version (c62baf6)

    This is a first "working" version of the jilu application.

    There are still many things to do, and there are still some hard-coded debug variables in the source code, but it's good to get it out there, and iterate on it from here on out.

    The three next big steps are:

    1. Improve testing setup.
    2. Expose configurables.
    3. Expand documentation.

    But it's out there, yay! 🎉 💃🏽

Bug Fixes

  • chronologically order release changes (fa7f5a5)

    Changes within a change set weren't ordered from newest to oldest, as was supposed to happen, this is now fixed.

    As an added bonus, this changes the commits returned by git::commits from a linked-list to a regular vector of chronologically ordered commits, improving performance and reducing complexity.

You can’t perform that action at this time.