ReleaseNotes Changelog Drafter

Entries

Preview


      

    

  


  

  

    

      
How this works

      

        

          
1. Set your release

          
Type a version number and pick a date at the top of the editor. These appear in the heading of your changelog. Use any format your project follows.

        

        

          
2. Add commits

          
Paste or type one commit message per line. Press Enter or click Add. Each entry starts untagged so you can sort them after.

        

        

          
3. Tag each entry

          
Click the feature, fix, or breaking button on any row. Breaking changes float to the top of their section in the preview.

        

        

          
4. Export

          
Copy the Markdown, download a file, or share a link. Your draft saves locally so you can close the tab and come back later.

        

      


      

        Common questions
        

          
Can I edit entries after adding them?

          
Yes. Click any commit text to edit in place. Use the trash icon to remove an entry. The preview updates immediately.

          
What happens if I close the tab?

          
Your draft is saved in localStorage. When you return, it loads the last draft. Only one draft is kept at a time.

          
Does this work with raw git log output?

          
It works best with one message per line. Paste your log and trim hashes or metadata first. Long multi-line commits may need a quick cleanup.

          
Can I use a different versioning style?

          
The version field is plain text. Use semver, calver, or your own scheme. The preview shows exactly what you type.

          
How do I share a draft with a teammate?

          
Use the Share link button. It encodes your draft into the URL. Your teammate sees the same entries but still needs to export the notes themselves.

          
Why do breaking changes sort to the top?

          
Breaking changes are the most important thing users need to see. Sorting them up front makes sure they do not get buried under small fixes.

        

      


      

        
Assumptions and limits

        
This runs entirely in your browser. Nothing you type leaves your device. Drafts are saved in localStorage, which means they stay in this browser only. Clearing site data removes them. The version field expects something like 1.2.0 but you can type any format you use. The date field uses the browser date picker.

        
It works best when each entry is a single line. Multi-line commit messages can be pasted but may look crowded in the preview. If you have a long list, add the most important ones first and keep the rest in a collapsed section of your own changelog.