plotting‐service: Release Notes for Maintainers

Repo-specific companion to Release Process, which has the branch model, squash rules, CHANGELOG format, semver guide and tagging convention. Read that first; this page only records what is different here.

Branches	develop (default), main
Release branch form	mixed — release/1.11.0 and release-1.8.0 both exist
Tag form	v1.11.0
Latest release	v1.11.0
Version source of truth	plotting-service/config.py → version / release
Published as	Docker image
CI publish trigger	push (docker.yaml)

Before releasing

• CI does not run the tests. The only workflow is docker.yaml. Run them yourself:

  cd test && python -m pytest test_samples.py

• This service depends on pyincore and pyincore-viz from the in-core conda channel, so a pyincore release can change this service's resolved environment with no change here. Recreate the env from scratch before release testing:

  conda env remove -n plotting-service
  conda env create -f plotting-service/env.yml

Watch out

• plotting-service/env.yml is the only dependency file; no requirements.txt, no lock file. It currently pins python=3.8.10, pyincore>=1.3.0 and pyincore-viz>=1.5.0, all well behind current releases. Bumping these is overdue and should be its own release.
• Release branch naming is inconsistent here (both forms used). Pick release-<version> going forward to match the majority, but check the CI actually fires.