Changelog

[strugee]

This project could use a change log. In particular 0.1.0 has just been released and it's exceedingly difficult to determine what has actually changed in this version compared with the previous release.

See also https://keepachangelog.com. Thanks for maintaining this project!

[whollacsek]

I'm also going through this trying to figure out what changed since 2016. In addition to the change log can we also promote this package to v1.0.0 and get regular minor releases?

Maybe using a tool like https://github.com/zeit/release

[eight04]

Does anyone have a summary about what has been changed for v0.1.0?

[silkentrance]

I am currently working on incorporating a changelog. ATM this will be hand crafted, since we do not have any commits that would support a standardized way for collecting changelog information in an automated fashion.

[silkentrance]

Does anyone have a summary about what has been changed for v0.1.0?

no.

[raszi]

In my comment https://github.com/raszi/node-tmp/pull/234/files#r377256378 I recommended to the https://github.com/ekataglobal/github-changelog project and I believe all the PRs are formatted correctly for that, so we can generate the changelog anytime.

[silkentrance]

@raszi I reckon that, thanks for the link btw. however, I needed to make this as fast as possible, and doing it by hand and not fiddling around with errs on behalf of github-changelog, I decided otherwise. And I think I tried the solution but it then gave me no suitable results?
I will give it another try soon.

[silkentrance]

We are actively using lerna-changelog over at testdeck, however, this requires that all pull requests are labelled with bug, enhancement, ... and so on.

[silkentrance]

Will look into this, closing for now.

[silkentrance]

I have found the time for looking into this.

github-changelog

• uses commit messages for classifying the nature of the commit
• in the past we did not care about any conventions when creating these messages, so the overall output is quite messy and the result is not beautiful

---

• @satazor: Uncaught exception (Uncaught exception #8)
• @aeosynth: use os.tmpDir (use os.tmpDir #7)
• @joscha: Bumped version (Bumped version #6)
• @joscha: Export _getTmpName for temporary file name creation (Export _getTmpName for temporary file name creation #5)
• @joscha: Please export _getTmpName (Please export _getTmpName #4)
• @node-migrator-bot: Hi! I fixed some code for you! (Hi! I fixed some code for you! #3)
• @fat: In 0.8.0 path.exists became fs.exists :) (In 0.8.0 path.exists became fs.exists :) #2)
• @chilts: Fix the default tmp dir (fixes a few tests) (Fix the default tmp dir (fixes a few tests) #1)

lerna-changelog

• creates beautiful results and we are also able to change the past by labelling our past pull requests

---

v0.2.0 (2020-04-25)

🚀 Enhancement

• #221 Gh 206 document name option (@silkentrance)

🐛 Bug Fix

• #193 Closes #192: tmp must not exit the process on its own (@silkentrance)

Committers: 2

• Carsten Klein (@silkentrance)
• Mattias Severson (@matsev)

v0.1.0 (2019-03-20)

🚀 Enhancement

• #141 test: refactor tests for mocha (@silkentrance)

📝 Documentation

• #180 fix Documentation still refers to a template that provides paths #179: template no longer accepts arbitrary paths (@silkentrance)
• #175 docs: add unsafeCleanup option to jsdoc (@kerimdzhanov)

Committers: 6

• Anna Henningsen (@addaleax)
• Carsten Klein (@silkentrance)
• Dan Kerimdzhanov (@kerimdzhanov)
• Gustav Klingstedt (@gutte)
• KARASZI István (@raszi)
• PoppinL (@poppinlp)

[silkentrance]

@raszi personally I would go for lerna-changelog as it produces the best results

of course, we will have to go through our pull requests and label them, but this will not take that much of a time.