Prepare Changelog for 0.69.0

[fortmarek]

Summary

Changelog

[Internal] - Changelog for 0.69.0

Test Plan

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,787,815	-36,203
android	hermes	armeabi-v7a	7,176,712	-34,348
android	hermes	x86	8,097,660	-36,824
android	hermes	x86_64	8,075,515	-39,012
android	jsc	arm64-v8a	9,654,711	-36,236
android	jsc	armeabi-v7a	8,412,504	-34,385
android	jsc	x86	9,605,314	-36,857
android	jsc	x86_64	10,200,192	-39,042

Base commit: ea29ae1
Branch: main

[facebook-github-bot]

@cortinico has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: ea29ae1
Branch: main

[fortmarek]

This changelog is now ready from my side.

I have split the commits into individual categories if you want to read through the changes I have made. The initial commit includes whatever the changelog-generator has produced.

Feel free to add additional reviewers that you think should have a look at this.

As a side note, I have noticed some commits like this having two logs:

[General] [Added] - A fail proof check to catch any crash involving webview:
if (exception.getClass().getCanonicalName().contains("MissingWebViewPackageException") || (message!=null && (message.contains("WebView provider") || message.contains("No WebView installed"))))
[General] [Removed] - Flawed check to catch WebViewProvider crash:
if (message != null && exception.getClass().getCanonicalName().contains("MissingWebViewPackageException"))

The changelog-generator only generates a log for the first message. Additionally, whatever is after a line break is just ignored. So, the log for this specific message was in section ### Added with A fail proof check to catch any crash involving webview:.

We either might want to do a better job at linting the changelog messages in the PR process if we don't to allow these cases or update the changelog generator to generate the messages properly.

[Simek]

Good job on the changelog formatting so far! 👍

I have left a few suggestions, do not marked all lines which need to be updated, but hope you get the gist of it. 🙂

[fortmarek]

Thanks @Simek for the thorough review! I will give this another pass now that I have a better idea what to look for.

[cortinico]

Generally looks good to me 👍 I'm importing this now, but we can keep on iterating on it for a bit

[facebook-github-bot]

@cortinico has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[kelset]

shouldn't this match what we wrote on the blogpost, so having 4 bullet points?

• Support for console.disableYellowBox has been dropped
• Already deprecated prop types have been removed (cdfddb4dad, 3e229f27bc, 10199b1581)
• removeListener, deprecated since RN0.xx, was removed from Appearance
• If you were using SegmentedComponentIOS, you will now need to move to the segmented-control library (235f168574)

[fortmarek]

Those logs are in the Removed section. As @Simek has pointed out when discussing privately, having both
Breaking and Removed sections rarely makes sense and is confusing. I can move those points here to match the blog post.

[kelset]

I think consistency with the blogpost has an higher priority 👍

[fortmarek]

done 👌

[facebook-github-bot]

@cortinico has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[cortinico]

@kelset @fortmarek I've merged this. If there are modifications to do, please let me know 👌

[react-native-bot]

This pull request was successfully merged by @fortmarek in d27c8cf.

^{When will my fix make it into a release? | Upcoming Releases}