Remove main.swift from Keystone

[kean]

I accidentally added it to the target together with other Classes/. I plan to move it outside of Classes/ eventually.

Note: Keystone will no longer compile because with the removal of main.swift, it changed how Keystone-Swift.h gets generated (Swift APIs available from Objective-C). It now includes only public APIs, and I could not find any way to change it. It is what I would expect considering that the Objective-C umbrella header works the same way – it requires headers included in it to be public.

To test:

Regression Notes

1. Potential unintended areas of impact

2. What I did to test those areas of impact (or what existing automated tests I relied on)

3. What automated tests I added (or what prevented me from doing so)

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing checklist:

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• VoiceOver.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• iPhone and iPad.
• Multi-tasking: Split view and Slide over. (iPad)

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 25.9. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	26999
	Version	PR #24383
	Bundle ID	com.jetpack.alpha
	Commit	f361df4
	Installation URL	5dq90pnplaeng

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	26999
	Version	PR #24383
	Bundle ID	org.wordpress.alpha
	Commit	f361df4
	Installation URL	0p73j4eulc1ug

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[mokagio]

Note: Keystone will no longer compile because with the removal of main.swift, it changed how Keystone-Swift.h gets generated (Swift APIs available from Objective-C). It now includes only public APIs, and I could not find any way to change it. It is what I would expect considering that the Objective-C umbrella header works the same way – it requires headers included in it to be public.

Yeah, run in similar constraints with WordPressData. See ##24326 and #24348 and I actually have another one coming from the new #24378

Given Keystone is not currently a dependency of the app targets, the fact it does not compile should not be an issue.

[mokagio]

What is says in the tin.

[mokagio]

Ah! Glad you committed this project change. I got it yesterday too but kept thinking "I'll open another PR then one for this one." I didn't want it out in a PR that did not work on the project file...