Merge remote-tracking branch 'origin/master' into imap-mail-toolkit

Author: a7m-1st

.container/.env.example

@@ -15,4 +15,4 @@ GOOGLE_API_KEY=123456789
 SEARCH_ENGINE_ID=123456789
 
 # For OpenWeatherMap API
-OPENWEATHERMAP_API_KEY=123456789
+OPENWEATHERMAP_API_KEY=123456789

.container/Dockerfile

@@ -1,4 +1,4 @@
-FROM python:3.10-bookworm
+FROM python:3.14-bookworm@sha256:14ab73bd56794689c00cce8162da1eb71925b188299f35f81717ec23816a5dea
 
 RUN pip install uv
 RUN groupadd -r appuser && useradd -r -g appuser appuser

.container/README.md

@@ -11,10 +11,10 @@ develop on it, with Docker.
 
 ## Configure Environment
 Before starting the container, you need to navigate into the
-[.container](../.container) folder and create a `.env` file **with your own 
-API 
-keys**, so that these keys will be present in the environment variables of 
-the container, which will later be used by CAMEL. The list of API keys that 
+[.container](../.container) folder and create a `.env` file **with your own
+API
+keys**, so that these keys will be present in the environment variables of
+the container, which will later be used by CAMEL. The list of API keys that
 can be found in the `.env.example` file.
 
 ```bash
@@ -25,15 +25,15 @@ cp .env.example .env
 ```
 
 ## Start Container
-After configuring the API keys, simply run the following command to start 
+After configuring the API keys, simply run the following command to start
 up the working container. This will automatically set up the environment and
 dependencies for CAMEL. It may take some time, please be patient.
 
 ```bash
 docker compose up -d
 ```
 
-After the build is completed, you can see the image `camel:localdev` in the 
+After the build is completed, you can see the image `camel:localdev` in the
 list of images, along with a started container, `camel-localdev`.
 
 ```bash
@@ -54,7 +54,7 @@ docker compose exec camel bash
 Then you will be in the container environment under the CAMEL directory, with
 all the dependencies installed.
 
-Then You can try running the 
+Then You can try running the
 [role_playing.py](../examples/ai_society/role_playing.py)
 example.
 
@@ -66,43 +66,43 @@ If you see the agents interacting with each other, this means you are all set.
 Have fun with CAMEL in Docker!
 
 ## Save Your Progress
-We support volume mounting in the started container, which means that all 
-of your changes in the CAMEL directory inside the container will be synced 
+We support volume mounting in the started container, which means that all
+of your changes in the CAMEL directory inside the container will be synced
 into the CAMEL repo on your host system. Therefore, you don't need to worry
 about losing your progress when you exit the container.
 
 ## Exit, Stop and Delete the Container
 You can simply press `Ctrl + D` or use the `exit` command to exit the
 container.
 
-After exiting the container, under normal cases the container will still be 
-running in the background. If you don't need the container anymore, you can 
+After exiting the container, under normal cases the container will still be
+running in the background. If you don't need the container anymore, you can
 stop and delete the container with the following command.
 
 ```bash
 docker compose down
 ```
 
 ## Online Images
-For users who only want to have a quick tryout on CAMEL, we also provide the 
+For users who only want to have a quick tryout on CAMEL, we also provide the
 pre-built images on
 [our GitHub Container Registry](https://github.com/camel-ai/camel/pkgs/container/camel).
-Considering the size of the image, we only offer the image with the basic 
+Considering the size of the image, we only offer the image with the basic
 dependencies.
 
-Note that there are some key differences between the local development 
+Note that there are some key differences between the local development
 image and the pre-built image that you should be aware of.
-1. The pre-built image is built upon the source code of each release of CAMEL. 
-   This means that they are not suitable for development, as they don't 
-   contain the git support. If you want to develop on CAMEL, please build 
+1. The pre-built image is built upon the source code of each release of CAMEL.
+   This means that they are not suitable for development, as they don't
+   contain the git support. If you want to develop on CAMEL, please build
    the image by yourself according to the instructions above.
-2. The pre-built image only contains the basic dependencies for running the 
-   examples. If you want to run the examples that require additional 
-   dependencies, you need to install them according to the 
+2. The pre-built image only contains the basic dependencies for running the
+   examples. If you want to run the examples that require additional
+   dependencies, you need to install them according to the
    installation guide in CAMEL's [README](../README.md).
-3. The pre-built image doesn't contain the API keys. You need to set up the 
+3. The pre-built image doesn't contain the API keys. You need to set up the
    API keys by yourself in the container environment.
-4. The pre-built image does not support volume mounting. This means that all 
+4. The pre-built image does not support volume mounting. This means that all
    of your changes in the container will be lost when you delete the container.
 
 To quickly start a container with the pre-built image, you can use the
@@ -123,4 +123,4 @@ command.
 
 ```bash
 python examples/ai_society/role_playing.py
-```
+```

.container/docker-compose.yaml

@@ -11,5 +11,3 @@ services:
       - .env
     user: "${UID:-1000}:${GID:-1000}"
     command: ["tail", "-f", "/dev/null"]
-
-

.container/minimal_build/Dockerfile

@@ -1,4 +1,4 @@
-FROM python:3.10-bookworm
+FROM python:3.14-bookworm@sha256:14ab73bd56794689c00cce8162da1eb71925b188299f35f81717ec23816a5dea
 
 RUN pip install uv
 RUN groupadd -r appuser && useradd -r -g appuser appuser

.env.example

@@ -10,6 +10,9 @@
 # Models API
 #===========================================
 
+# Cerebras API (https://chat.cerebras.ai/)
+# CEREBRAS_API_KEY="Fill your API key here"
+
 # OpenAI API (https://platform.openai.com/signup)
 # OPENAI_API_KEY="Fill your API key here"
 
@@ -70,6 +73,10 @@
 # GOOGLE_API_KEY="Fill your API key here"
 # SEARCH_ENGINE_ID="Fill your API key here"
 
+# Google Gmail API (https://console.cloud.google.com/)
+# GOOGLE_CLIENT_ID="Fill your API key here"
+# GOOGLE_CLIENT_SECRET="Fill your API key here"
+
 # OpenWeatherMap API (https://home.openweathermap.org/users/sign_up)
 # OPENWEATHERMAP_API_KEY="Fill your API key here"
 
@@ -133,4 +140,4 @@
 
 # Grok API key
 # XAI_API_KEY="Fill your Grok API Key here"
-# XAI_API_BASE_URL="Fill your Grok API Base URL here"
+# XAI_API_BASE_URL="Fill your Grok API Base URL here"

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: 🐛 Bug Report
 description: File an issue about a bug.
 title: "[BUG] "
-labels: [bug]
+labels: [bug, Needs Triage]
 body:
   - type: markdown
     attributes:
@@ -26,7 +26,7 @@ body:
     attributes:
       label: What version of camel are you using?
       description: Run command `python3 -c 'print(__import__("camel").__version__)'` in your shell and paste the output here.
-      placeholder: E.g., 0.2.76a10
+      placeholder: E.g., 0.2.82
     validations:
       required: true
 

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,7 +1,7 @@
 name: ✨ Feature Request
 description: Suggest an idea for this project.
 title: "[Feature Request] "
-labels: [enhancement]
+labels: [Needs Triage]
 body:
   - type: checkboxes
     id: steps

.github/ISSUE_TEMPLATE/questions.yml

@@ -1,7 +1,7 @@
 name: 🤔 Questions / Help / Support
 description: Do you need support?
 title: "[Question] "
-labels: [question]
+labels: [question, Needs Triage]
 body:
   - type: checkboxes
     id: steps

.github/actions/camel_install/action.yml

@@ -21,7 +21,7 @@ runs:
       name: Restore caches for the virtual environment based on uv.lock
       with:
         path: ./.venv
-        key: venv-${{ hashFiles('uv.lock') }}
+        key: venv-${{ hashFiles('uv.lock', 'pyproject.toml') }}
     - name: Validate cached virtual environment
       id: validate-venv
       if: steps.cache-restore.outputs.cache-hit == 'true'
@@ -49,4 +49,4 @@ runs:
       if: steps.cache-restore.outputs.cache-hit != 'true' || steps.validate-venv.outputs.cache-valid == 'false'
       with:
         path: ./.venv
-        key: venv-${{ hashFiles('uv.lock') }}
+        key: venv-${{ hashFiles('uv.lock', 'pyproject.toml') }}