Good news - this was implemented back in Objo Studio v26.6.3.
Select the project and choose Insert → Resource Files… or Insert → Resource Folder…. You can also drag files or folders onto the project’s Resources node. Their folder structure is preserved, and they are included automatically when running, debugging, profiling, building, publishing, or remote debugging.
For your CI/CD example, a VCS-friendly .objosln solution can receive the generated file directly before building:
Projects/<project-folder>/Resources/Files/RELEASE_NOTES.md
objo build and objo publish will load and deploy it. A portable .objo project is a ZIP archive, so resources are stored inside it rather than discovered from a loose folder beside it.
Application code should use the cross-platform resource location rather than hard-coding a platform-specific bundle path:
Var notes As FileSystemItem = SpecialFolder.Resources.Child("RELEASE_NOTES.md")
Resources should be treated as read-only. If the application needs to modify one, copy it to a writable location first.
More details are available in the Resource Files documentation.