When will TAO-CE have a complete OSS release?

Hello everyone. I tried to follow the steps outlined here to build Tao locally but there were many private dependencies. I noticed that there were read-only alternative public repositories for many of the private packages in the github tao-ce organisation. But some packages don’t have a public version available in the organisation (like bundle-bigtable-document-manager). I learned this the hard way after fiddling with the .gitmodules, composer.json, composer.lock etc. files. So now, I wanted to ask if there was a tentative date of when these packages will be made public so that TAO can truly be built locally by anyone. Thank you!

Hello,

Indeed, we are working on a new release, expected for August 2026 (to be confirmed), which mainly targets building from sources.

An announcement will be shared on this forum.

Hi Arsalan,

Thanks for reaching out!

Looking at the issue you described, it seems like there might be a misconfiguration at tao-ce/libexec/setup/apps/deliver.libsonnet at develop · tao-ce/tao-ce · GitHub . Could you please verify that this is set to dev? The bundle you’re running into is actually only required if your environment is set to prod (see line https://github.com/tao-ce/tao-deliver-be/blob/main/config/bundles.php#L18).

My advice would be to double-check those settings, revert any composer changes you made, and give it another try. Let me know how it goes!

Best Regards,
Vitalii

Hi kilatib, I just checked, the APP_ENV is already set to ‘dev'. I have not meddled with that.

Also this is not the only bundle, several others are shown as missing when we check the logs after the command task dev:up fails. I have attached a picture showing some of them.

I also had to modify .gitmodules to be able to fetch the submodules in the first place.

Hi, @arsalan

I just briefly looked at the configuration, and I think I see the problem, may you try to update tao-deliver-be/composer.json at main · tao-ce/tao-deliver-be · GitHub and replace there oat-ce to tao-se after update composer cache should help I think