Add .bumpversion.cfg file

[niketagrawal]

When tudat is bumped to a new dev version, the following actions must happen on tudat-feedstock develop branch:

• Bump version: this results in bumping of the dev version in recipe/meta.yml and .bumpversion.cfg file
• Create a tag with the above version
• Push the tag to tudat-feedstock

Currently, the above operation is being done manually. Automating the bump version operation will synchronize the dev versions of tudat and tudat-ffedstock

[niketagrawal]

Changes are being developed and tested in https://github.com/niketagrawal/tudat-feedstock/tree/develop

To do:

• Add .bumpversion.cfg
• Modify recipe/meta.yml to correctly bump the version and git_rev numbers using the bumpversion command.
• Try polling instead of receiving a notification from tudat repository. The latter didn't work due to incorrect/missing token permissions. An alternative to receiving a notification from tudat upon a commit on develop is to poll the tudat repository nightly for new commits on develop branch of tudat.

[niketagrawal]

Done

• GitHub actions workflow in tudat repository to bump the version in tudat repository when a new commit on dev branch is created
• GitHub actions workflow in tudat-feedstock that watches for new commits on dev branch of tudat and bumps version in meta.yml

Questions

• Con of polling on tudat-feedstock: Between subsequent poll intervals, multiple commits might be made on dev branch of tudat. How do bump the version number on feedstock in this case?
• At what point does the minor or patch version number needs to be updated? The bumpversion command in the workflow will need to be modified then, because by default it bumps the devxx number after the patch.

[niketagrawal]

The polling based workflow to detect new commits in tudat dev branch has the following cons:

• Each new commit on tudat will have to wait before the corresponding dev conda package is created
• Between two consecutive worklfow runs, dev branch of tudat could receive multiple commits.

To do

• Revert the polling based workflow on tudat-feedstock to dispatch event based workflow so all commits on tudat are sure to trigger a new dev conda package.
• Create a separate bump version workflow in tudat that will bump the minor version on main when a new commit is made. : Automated workflow for master branch is not needed. It is desired to keep the bump version operation manual on the master branch.

[niketagrawal]

This issue will get fixed with tudat-team/tudat#232 is closed. A nightly bump version workflow in tudat will be created as part of this isse which will bump version, create tag and push tag to tudat-feedstock.

Tudat-feedstock misses a .bumpversion.cfg and the recipe/meta.yml must be adapted to work with the bumpversion command. These changes will be introduced via a PR.

[niketagrawal]

Changes in branch https://github.com/tudat-team/tudat-feedstock/tree/11-add-bumpversion-cfg

Creating a draft pull request triggers azure pipelines. They must be manually stopped when the PR containing these changes is being merged to avoid creating a new conda package.

[niketagrawal]

Changes merged in pull request #13