nebari-dev / governance

✨ Governance-related work for Nebari-dev
BSD 3-Clause "New" or "Revised" License
0 stars 2 forks source link

RFD - Setup jupyter-releaser for jupyterlab extensions #57

Open krassowski opened 3 weeks ago

krassowski commented 3 weeks ago
Status Draft 🚧 / Open for comments 💬
Author(s) @krassowski
Date Created 2024-10-29
Date Last updated
Decision deadline 2024-11-12

Title

Setup jupyter-releaser for jupyterlab extensions

Summary

User benefit

Every admin and every contributor added to release team would be able to release a new version of jupyterlab extensions developed in nebari with approximately 8 clicks.

Design Proposal

There are two ways to use jupyter-releaser:

  1. from a GitHub action in the target repository (documentation)
  2. from a GitHub action in the fork of the releaser repository (documentation)

I propose to use the (1) approach as this is better for collaboration and needs setting up only once.

There are some workflow assumptions in jupyter-releaser and configuration requirements:

The following repositories would be using the jupyter-releaser workflow:

Alternatives or approaches considered (if any)

Best practices

The labels are in conflict with the currently used labels in nebari-dev; we can investigate configure it in jupyter-releaser to support the labels available in nebari-dev.

User impact

None

Unresolved questions

I will need help setting up the GitHub App and ideally access to a vault where I could put secrets to set it all up.

viniciusdc commented 2 weeks ago

I support this change