This repository was archived by the owner on Jan 23, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 23
Release process #645
Open
mangelajo
wants to merge
2
commits into
jumpstarter-dev:main
Choose a base branch
from
mangelajo:release-process
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Release process #645
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,104 @@ | ||
| # Maintainers Guide | ||
|
|
||
| ## Releasing | ||
|
|
||
| To release a new version of Jumpstarter, you need to follow these steps: | ||
|
|
||
| ### set the version you want to release | ||
| ```console | ||
| export VERSION_PYTHON=0.7.0 | ||
| export VERSION_GO=0.7.0 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what do these mean? |
||
| export RELEASE_BRANCH=release-0.7 | ||
| ``` | ||
|
|
||
| If you wish to create a pre-release you can add the desired suffixes, but please note that go | ||
| and python use sighlty different naming conventions. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix typo in documentation. Line 15 reads “sighlty”; please correct it to “slightly” so the instructions stay professional. 🤖 Prompt for AI Agents |
||
|
|
||
| For example: | ||
| ```console | ||
| export VERSION_PYTHON=0.7.0rc1 | ||
| export PYTHON_NEXT=0.8.0-dev | ||
| export VERSION_GO=0.7.0-rc1 | ||
| export RELEASE_BRANCH=release-0.7 | ||
| # the next version of python used as anchor for main branch versions with pip index | ||
| export PYTHON_NEXT=0.8.0-dev | ||
| ``` | ||
|
|
||
| ### checkout and release the jumpstarter-e2e repository | ||
|
|
||
| ```console | ||
| git clone https://github.com/jumpstarter-dev/jumpstarter-e2e.git | ||
| cd jumpstarter-e2e | ||
| ``` | ||
|
|
||
| For this one we don't tag versions, we just create a new branch. | ||
|
|
||
| ```console | ||
| git fetch --all --tags # in case you already have the repository cloned | ||
| git checkout remotes/origin/main -B "${RELEASE_BRANCH}" | ||
| git push origin "${RELEASE_BRANCH}" | ||
| git checkout remotes/origin/main -B main | ||
| git tag -a "v${PYTHON_NEXT}" -m "Development base v${PYTHON_NEXT}" | ||
| git push origin "v${PYTHON_NEXT}" | ||
| ``` | ||
|
|
||
| ### checkout and release the controller repository first | ||
|
|
||
| ```console | ||
| git clone https://github.com/jumpstarter-dev/jumpstarter-controller.git | ||
| cd jumpstarter-controller | ||
| ``` | ||
|
|
||
| If it's the first time you are creating a tag for a minor version, you need to create a new branch first. | ||
| ```console | ||
| git fetch --all --tags # in case you already have the repository cloned | ||
| git checkout remotes/origin/main -B "${RELEASE_BRANCH}" | ||
| git push origin "${RELEASE_BRANCH}" | ||
| ``` | ||
|
|
||
| Now just tag the branch | ||
| ```console | ||
| git fetch --all --tags # in case you already have the repository cloned | ||
| git checkout remotes/origin/${RELEASE_BRANCH} -B ${RELEASE_BRANCH} | ||
| git tag -a "v${VERSION_GO}" -m "Release v${VERSION_GO}" | ||
| git push origin "v${VERSION_GO}" | ||
| ``` | ||
| ### checkout and release the jumpstarter python packages repository | ||
|
|
||
| ```console | ||
| git clone https://github.com/jumpstarter-dev/jumpstarter.git | ||
| cd jumpstarter | ||
| ``` | ||
|
|
||
| If it's the first time you are creating a tag for a minor version, you need to create a new branch first. | ||
| ```console | ||
| git fetch --all --tags | ||
| git checkout remotes/origin/main -B "${RELEASE_BRANCH}" | ||
| git push origin "${RELEASE_BRANCH}" | ||
| ``` | ||
|
|
||
| Now just tag the branch | ||
| ```console | ||
| git fetch --all --tags | ||
| git checkout remotes/origin/${RELEASE_BRANCH} -B ${RELEASE_BRANCH} | ||
| git tag -a "v${VERSION_PYTHON}" -m "Release v${VERSION_PYTHON}" | ||
| git push origin v${VERSION_PYTHON} | ||
| ``` | ||
|
|
||
| # Create release notes | ||
|
|
||
| * https://github.com/jumpstarter-dev/jumpstarter/releases/new | ||
| * https://github.com/jumpstarter-dev/jumpstarter-controller/releases/new | ||
|
|
||
| # Triggering a new package index build here | ||
|
|
||
| Using the Run Workflow from main: | ||
| https://github.com/jumpstarter-dev/packages/actions/workflows/publish-index.yml | ||
|
|
||
| # Publish to pypi | ||
| ```console | ||
| export UV_PUBLISH_TOKEN=pypi-..... | ||
| git checkout v0.7.0 | ||
| rm -rf dist | ||
| make build | ||
| uv publish | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace the empty
##heading.Line 80 contains a heading marker with no title, which renders as a blank section header in Sphinx/Markdown. Drop it or give it a meaningful label (e.g.,
## Reference) before the toctree.🤖 Prompt for AI Agents