Skip to content

release.md

Latest commit

 

History

History
35 lines (32 loc) · 1.81 KB

release.md

File metadata and controls

35 lines (32 loc) · 1.81 KB
Raw

Release Documentation

Follow the steps below meticulously to avoid a broken release.

  1. Adapt version information. The CI pipeline will fail if the version strings in the files below do not match.
    • pyproject.toml
    • Add flatpak meta-data in meta/com.nitrokey.nitrokey-app2.metainfo.xml, like this: <release version="2.3" date="2024-04-19"/>
      • The latest release should be on top of this list.
  2. Create a new tag and release.
    1. Make sure the main branch of your cloned repository is up-to-date. Create a new tag with git tag -s -m "vX.Y.Z" vX.Y.Z and push it to GitHub with git push origin vX.Y.Z. Open the repository on GitHub and open the releases page. Click "Draft a new release" and select the just created tag.
    2. Open the repository on GitHub and open the releases page. Click "Draft a new release". In the dropdown field "Choose a tag" select "Create a new tag". Enter the version string in the form vX.Y.Z. Fill the fields title and description. Set the checkbox "Set as a pre-release" and create the release.
  3. Wait for the pipelines to succeed. At this point the tag and release can still be removed. If manual testing is required, perform these tests now with the pipeline artifacts. Otherwise continue with the next steps.
  4. Open the release page for the version and click the edit button. Change the release from pre-release to latest release and save the change.
  5. The pipeline for the deployment to PyPI needs manual approval. Open the repository on GitHub and open the Actions page. Open the respective PyPI release job. Click the Review deployments button. Set the checkbox "pypi" and click Approve and deploy.
  6. Please mind that the Flatpak build needs to be triggered manually.

The release is now complete.