Heanh Sok

> 1. The linter container (`//helpers` in this case) should be a prod release so that all the code inside the container is frozen, and we are "guaranteed" that there...

I'm adding it to the same project as its parent issue https://github.com/causify-ai/csfy/issues/5514, although they don't fit well inside that project. Since we'll be having more things to work on such...

All related issued moved to [DevSystem-v2.6 - Automate GH](https://github.com/orgs/causify-ai/projects/90)

IMO as we are iterating on several options to do this (such as GH Actions, python script, bash script, dockerized executable, and invoke target), the way to go is probably:...

Yes could you please share relevant doc on how to do it? @dremdem We can use this flag to build the multi arch image right? ```bash i docker_build_local_image --version 1.0.0...

> And in the output should be: > > ``` > \"architecture\": \"amd64\" > ``` > > it means for `Linux` > > and > > ``` > \"architecture\": \"arm64\",\n...

I have built and pushed the multi arch version now. could you please check again? @dremdem

```bash > i docker_tag_push_multi_build_local_image_as_dev --version 1.0.0 --target-registry dockerhub.causify 17:45:03 - INFO hdbg.py init_logger:1018 > cmd='/data/heanhs/src/venv/client_venv.helpers/bin/invoke docker_tag_push_multi_build_local_image_as_dev --version 1.0.0 --target-registry dockerhub.causify' # docker_tag_push_multi_build_local_image_as_dev: version='1.0.0', local_base_image='', target_registry='dockerhub.causify', container_dir_name='.' # docker_login: target_registry='dockerhub.causify' 17:45:03...

> I'd say we want to make sure the flow works by pushing the top one and one of the runnable dirs Yes which of the runnable dirs do you...

Yes it was done. - The image `tutorials` was built and pushed to ECR and Dockerhub. - The release flow was also tested for `tutorial_langchain`.