Skip to content

Release 0.3.0: tracking #933

Open
Open

Description

@jtravs

Checklist for the 0.3.0 release (releasing).

  • Release-readiness PR merged (Release readiness for 0.3: audit fixes #883), CI green on its head.
  • Release commit merged (Release 0.3.0 #568, 029ea8e): changelog section [0.3.0], CITATION.cff 0.3.0, output schema 3.
  • CI passed on the release commit (029ea8e).
  • Wheels workflow dry run on the release commit at the head of main: run 44380533250, 23 jobs passed, the publish jobs skipped.
  • GPU lane (poe test-gpu) on a CUDA build: passed on an NVIDIA A40 at the release commit 029ea8e (308 passed, 1 skipped in tests; 31 passed, 1 skipped in native; both skips intended; CUDA 12.8, GCC 14.4, cuFFT and cuBLAS). No AMD device was available for a HIP build.
  • Tag v0.3.0 pushed on its own (on 029ea8e); wheels run 44399881696.
  • pypi-native, pypi, pypi-gui approved; uploads complete (solprop-native 0.3.0: five wheels; solprop 0.3.0 and solprop-gui 0.3.0: sdist and wheel each).
  • published-install and published-install-gui green on five platforms: https://github.com/LupoLab/solprop/actions/runs/44399881696 (the Windows on Arm install was re-run once: its first attempt asked PyPI for 0.3.0 before the index showed it).
  • GitHub release published (https://github.com/LupoLab/solprop/releases/tag/v0.3.0); Zenodo DOI 10.5281/zenodo.24355984.
  • Read the Docs: /en/stable/ serves 0.3.0, built from the tagged commit (the v0.3.0 version itself is not activated, as for 0.2.0).
  • Earlier releases: 0.2.0 is not yanked (maintainer: yanking 0.1.0 was a one-off for the numba backend removal).
  • Benchmark history rows recorded for the release: seven of nine hardware sets recorded from the tag wheels; two CPU sets and the history pull request to follow.
  • Milestone 0.3 closed.

Activity

  1. added this to the 0.3 milestone on Nov 18, 2026
  2. jtravs commented on Nov 18, 2026

    @jtravs
    ContributorAuthor

    The tag's wheels run (44399881696) had one failed job, test (windows-arm64): one test, test_a_reducing_run_keeps_no_more_alive_as_it_goes[native], out of 20,986 (the same job passed on the same commit in the dry run). It is a measurement artefact of the test, filed separately; the failed job is being re-run, and the publish jobs wait for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions