2.5.0 doesn't have a changelog entry about dry-initializer HOT 6 CLOSED

@bjeanes Hi! Thank you, you're right
Will restore it on weekend

from dry-initializer.

Hi @nepalez just a casual and hopefully friendly reminder about this one. I'd offer to help but at this point I am not particularly sure how you generate your changelogs or choose what is included.

from dry-initializer.

By mistake I've added the entry for 2.5.0 under 2.6.0, so now I've fixed it by just adding one line to then README.md. This is a good news.

The bad one is v2.6.0 broke rom, so it has been yanked by @solnic. I've rolled back master to v2.5.0 as well. I think, we need more investigation about your PR that add @default_null. For now I see no reason why it breaks the backward compatibility.

Let's start from scratch. Could you remind, please, why this distinction between @null and @default_null was needed?

from dry-initializer.

Hi @nepalez, I think you might be confusing me with the author of #46. I also made a change touching @null though, so this is understandable. My changes are in 2.5.0 which didn't break rom, as I understand it.

As a refresher, my change was #39, which just swapped the right and left hand of the comparison for null, because AR's #== had side effects 😱.

from dry-initializer.

Looking at latest CHANGELOG.md, I don't think it's right. Are you sure added the 2.5.0 changes as 2.6.0 originally? The latest 2.5.0 entry mentions the reverted commit 128b484 from #46.

from dry-initializer.

I added a comment on your latest commit with what I believe is probably the real contents of 2.5.0 changes: 42cfc4e#r31064892

from dry-initializer.