Release notes formatting

[MFKDGAF]

No formatting at all.

[Nail1684]

@MFKDGAF I think the way release notes are structured was changed recently – e.g. see here:

2026.4.0 Release Notes

@mutilator Just a normal major release indicated by the second number in the version as pointed out by @DenBesten. I teased this upcoming change to the Github release notes here: Previously the commits weren’t categorized and it was harder for consumers to see what was updated and if the bug they reported/experienced was fixed within a specific release. This aims for a nicer experience and to give more transparency. There’s some more things I have planned around this, stay tuned. This was st…

And maybe (obviously?) that doesn’t work smoothly in every corner yet…

[MFKDGAF]

I read what you linked to but I don’t think that applies here because look at how the release notes were structured and formatted in previous releases. In previous release notes there were multiple bullet points.

This release notes have 1 bullet point and multiple sentences.

[Nail1684]

@MFKDGAF

In previous release notes there were multiple bullet points.

If you compare the iOS PM release notes 2026.4.0 in your screenshot with the corresponding release notes on GitHub, then you also see the same structure (and that on iOS, they were pulled from the “Overview” section from GitHub):

But this section was restructured recently. As iOS versions 2026.4.1 were not released on GitHub yet, here the screenshots from the Android repository:

As you see, also on GitHub are (were) some formatting errors. But you can also see in your screenshot for iOS version 2026.4.1 the new subsections for “Overview” (What’s New, Improvements, Bug Fixes).

So, my guess still is, that the still-not-ideal formatting from GitHub gets pulled – and that also doesn’t get corrected yet. (as soon as iOS password manager version 2026.4.1 appears on GitHub, I’ll add the screenshot for that)

PS: Ah, there it is (https://github.com/bitwarden/ios/releases/tag/v2026.4.1-bwpm):

[dwbit]

Hey @MFKDGAF, rest assured the team is aware of the formatting on the release notes, thanks for flagging.