paths.env not being replaced in GitHub workflow after deployment

I do have a paths.env file which contains two variables. I successfully deployed my code to Azure, using the following workflow (for simplicity, only posting the build part here)

on:  push:    branches:      - main  workflow_dispatch:jobs:  build:    runs-on: ubuntu-latest    steps:      - uses: actions/checkout@v4      - name: Set up Python version        uses: actions/setup-python@v1        with:          python-version: '3.8'      - name: Create and start virtual environment        run: |          python -m venv venv          source venv/bin/activate      - name: Update pip        run: |          python -m pip install --upgrade pip      - name: Install dependencies        run: pip install -r requirements.txt      # Optional: Add step to run tests here (PyTest, Django test suites, etc.)      - name: Zip artifact for deployment        run: zip release.zip ./* -r      - name: Upload artifact for deployment jobs        uses: actions/upload-artifact@v3        with:          name: python-app          path: |            release.zip            !venv/  create-env-file:    needs: build  # Wait for the build job to complete    runs-on: ubuntu-latest    steps:      - name: 'Create env file'        run: |          echo "WORK_PATH=$(pwd)" > paths.env          echo "STORE_DATA_PATH=$(pwd)/store_data/" > paths.env          cat paths.env

Why are WORK_PATH and STORE_DATA_PATH not being replaced?