What makes you think it isn’t? The issue is tracked as #2179, #2212 was only the pull request which resolved it.
At first I was very sure you’re wrong: code that has been commited to master since 0.9.5 was surely included in 0.9.6, I just tag the new version from master and there’s no process to selectively include/exclude commits from there. So it must be included.
But then I checked the changelog: It does mention #2179, but in the section for 0.9.5. But @durval wrote in this thread and the title that the fix is not included in 0.9.5. Hm. Looking at the history for CHANGELOG.md shows the commit for 0.9.6 inserted the fix into the section for 0.9.5. That’s odd for sure!
So, let’s dig in. The pull request ID was #2212, so we can use git log -p and grep for 2212, finding the merge commit (a6481b37072dc4878bf845de77ed67406c59905d) which added the code to master:
Indeed we can verify that (only) 0.9.6 contains this commit:
$ git tag -l --contains a6481b37072dc4878bf845de77ed67406c59905d
v0.9.6
It looks like git’s merge resolve code decided that the directory changelog/unreleased was renamed to changelog/0.9.5_2019-04-23 (which it was!) and put the file into that directory instead of the unreleased one.
So, long story short: the fix is included in 0.9.6, and I’ll fix the changelog. Sigh. This will hopefully not happen again, with Folder changelog/unreleased/ doesn't exist when empty · Issue #2485 · restic/restic · GitHub we ensure the unreleased folder exists and is never empty.