Fork me on GitHub
#pedestal
<
2023-06-06
>
lread17:06:52

Something is different between 0.5.11-beta-1 and 0.6.0-beta-2 in how + is handled in path portion of URL which caused an issue for cljdoc. I'll report back when I've figured out what's up.

hlship17:06:28

That's another case where double HTML decoding would show up. See the notes in the https://github.com/pedestal/pedestal/blob/master/CHANGELOG.md#060---unreleased

lread17:06:44

Ah thanks, I missed that breaking change in the changelog! Should "0.6.0 - UNRELEASED" maybe be changed to "0.6.0-beta-2 - June 2, 2023"? I was actually reading latest changes from https://github.com/pedestal/pedestal/releases page and didn't even notice I wasn't reading about 0.6.0 because 0.6.0 is not listed there.

hlship17:06:33

I tend to only put a final entry in for an entire release cycle; the notes accumulate under the "UNRELEASED" heading until the final 0.6.0 release. I think this addresses the needs of the majority of Pedestal users, who will not upgrade until the next final release, and will want to see the changes all in one place.

👍 2
lread18:06:15

I personally find this confusing but totally respect how you want to sail your ship!

hlship20:06:29

Maybe I'm wrong, but this is essentially how I've operated across many different projects since maybe 2002.

lread21:06:12

There is no right or wrong. All good now that I understand it.