Hi @Roman, I am using the GitHub integration.
Currently I have a GitHub action that exports the english localization file (en.xliff) which is then uploaded to the Crowdin project using the crowdin/github-actions workflow with upload_sources: true. Then when translators change the files, it is uploaded back into the GitHub project repo via the GitHub integration into the respective lproj folders.
This was nice because everything was automated. How would I be able to work with the bundle?
Recently we’ve improved the Target File Bundles feature for the GitHub integration (as well as other DVCS integrations) to use the Bundles created in your Crowdin project.
As a result, bundles: - 3 have been added to your configuration file. It means that the integration will use the Bundle with ID 3 to export the translation. This Bundle can be found in the Translations tab > Target File Bundles on your Crowdin project page. You can remove the targets section from your configuration file.
The behavior of the translation export should be the same as before.