Skip to content

Merge pull request #690 from mbektas/upgrade-to-electron-26 #668

Merge pull request #690 from mbektas/upgrade-to-electron-26

Merge pull request #690 from mbektas/upgrade-to-electron-26 #668

name: Check for new JupyterLab releases
on:
schedule:
- cron: 30 17 * * *
workflow_dispatch:
permissions:
contents: write
pull-requests: write
jobs:
check_for_lab_updates:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: '3.9'
- name: Install Python dependencies
run: |
python -m pip install tbump
- name: Check for new releases
shell: bash
run: |
set -eux
export LATEST=$(python scripts/get_latest_lab_version.py)
echo "latest=${LATEST}" >> $GITHUB_ENV
tbump --only-patch ${LATEST}-1 --non-interactive
if [[ ! -z "$(git status --porcelain package.json)" ]]; then
echo "update_available='true'" >> $GITHUB_ENV
fi
- name: Install Node
if: env.update_available == 'true'
uses: actions/setup-node@v3
with:
node-version: '14.x'
- name: Install npm dependencies
if: env.update_available == 'true'
run: |
npm install --global yarn
yarn install
- name: Install conda
if: env.update_available == 'true'
uses: s-weigand/setup-conda@v1
run: conda install -c conda-forge conda conda-lock -y
- name: Create a PR if needed
if: env.update_available == 'true'
shell: bash
env:
GITHUB_USER: ${{ secrets.GITHUB_USER }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
set -eux
yarn update_conda_lock
export LATEST=${{ env.latest }}
export BRANCH_NAME=update-to-v${LATEST}
# this will fail if the branch already exists which means we won't have duplicate PRs
git checkout -b "${BRANCH_NAME}"
git config user.name "JupyterLab Desktop Bot"
git config user.email '[email protected]'
git commit . -m "Update to JupyterLab v${LATEST}"
git push --set-upstream origin "${BRANCH_NAME}"
hub pull-request -m "Update to JupyterLab v${LATEST}" \
-m "New JupyterLab release [v${LATEST}](https://github.com/jupyterlab/jupyterlab/releases/tag/v${LATEST}) is available. Please review the lock file carefully.".