Skip to content

Nightly Bump Version Workflow ‐ GitHub Actions Automation

Niket Agrawal edited this page Nov 15, 2024 · 5 revisions

This page describes the Nightly bump version workflow implemented for the tudat repository to automate the process of bumping the dev version number and releasing a new tudat dev conda package.

Workflow execution sequence

  1. Trigger: The workflow is triggered automatically at 01:00 AM CET every day.

  2. Action: After the workflow is triggered, it checks for any new commits on the develop branch of the tudat repository in the last 24 hours. If there are new commits detected, the following actions are performed:

    1. Bump version in tudat: Bump the dev version number in version and .bumpversion.cfg, create a tag, and push the tag and the bump version commit to the develop branch of the tudat repository
    2. Bump dev version in tudat-feedstock: Bump the dev version number in meta.yml, create a tag, and push the tag and the bump version commit to the develop branch of the tudat-feedstock repository. This commit on the develop branch of tudat-feedstock triggers the azure pipelines resulting in the creation of a tudat dev conda package with this version number.

Workflow implementation details

  • The workflow is implemented as a GitHub action workflow. It runs automatically every day at a specified time (01:00 AM CET).

  • The workflow lives in the master branch, but performs write actions on the develop branch. This is because GitHub requires scheduled GitHub action workflows to be implemented in the default branch.

  • Personal Access Token: This GitHub Actions workflow uses a personal access token to bump version, create a tag, and push the tag to tudat-feedstock repository. See issue #232 for information on how this token is setup.

  • Issue tracker #232

  • Pull request #246