Release automations

[cisaacstern]

User Profile

As a project owner

User Action

I want all images and repos which are affected by releases of pangeo-forge-recipes to be automatically updated with each release of pangeo-forge-recipes

User Goal

So that I do not have to devote manual toil to syncing all parts of the platform following every release of pangeo-forge-recipes

Acceptance Criteria

To start, I thought it would be useful to brain dump a list of everything that we'd want to happen automatically following a pangeo-forge-recipes release, in order of dependency:

• On release, automatically update version references in docs pangeo-forge-recipes#357
• Update Conda Forge feedstock, xref pangeo-forge-recipes v0.8.3 conda-forge/pangeo-forge-recipes-feedstock#4
  • We created the Conda Forge feedstock when 0.8.2 was the latest pangeo-forge-recipes release. Since then, a Conda Forge bot noticed that 0.8.3 was available on PyPI, and opened ☝️ that PR. We have not yet merged that PR. I am unclear if a manual merge is required on the pangeo-forge-recipes-feedstock for every release.
• Build and push new bakery image, xref Automatically build images? pangeo-forge-bakery-images#7
  • It seems preferable to wait until the new release is available on Conda Forge to build the bakery image, because then we can install with conda like this PR for 0.8.2 rather then having to install from pip like this PR for 0.8.3
• Update Registrar BAKERY_IMAGES dict, xref https://github.com/pangeo-forge/registrar/issues/37
  • As noted in the linked Issue for this point, we could consider changing this architecture to make this easier to automate.
• Update Sandbox template and (maybe) Dockerfile
  • Automatically bump pangeo_forge_version in meta.yaml template? sandbox#8
  • Pangeo Notebook / nbgitpuller incompatibility sandbox#9

Linked Issues

See above