@@ -48,16 +48,16 @@ should change depending on the updates to the code base.
4848Releasing is semi-automated via a CI job.
4949The CI job requires the type of version bump
5050that will be performed to be manually specified.
51- See the pdm- bump docs for the
52- [ list of available bump rules] ( https://github.com/carstencodes/pdm-bump#usage ) .
51+ See the ` uv version ` docs (specifically the ` -- bump` flag) for the
52+ [ list of available bump rules] ( https://docs.astral.sh/uv/reference/cli/#uv-version ) .
5353
5454### Standard process
5555
5656The steps required are the following:
5757
58581 . Bump the version: manually trigger the "bump" workflow from the main branch
5959 (see here: [ bump workflow] ( https://github.com/openscm/pandas-openscm/actions/workflows/bump.yaml ) ).
60- A valid "bump_rule" (see [ pdm-bump 's docs] ( https://github.com/carstencodes/pdm-bump#usage ) )
60+ A valid "bump_rule" (see [ uv 's docs] ( https://docs.astral.sh/uv/reference/cli/#uv-version ) )
6161 will need to be specified.
6262 This will then trigger a draft release.
6363
@@ -87,12 +87,10 @@ The steps required are the following:
8787
8888#### Further details
8989
90- We use [ pdm] ( https://pdm-project.org/en/latest/ ) for building our project,
91- while [ uv figures out how it wants to support building] ( https://github.com/astral-sh/uv/issues/3957 ) .
92- This gives us the added benefit that we can use
93- [ pdm-build-locked] ( https://pdm-build-locked.readthedocs.io/en/stable/ )
94- to build locked versions of our package.
95- It is for these reasons that we create a ` pdm.lock ` file
90+ We use [ uv's build backend] ( https://docs.astral.sh/uv/concepts/build-backend ) for building our project
91+ and ` scripts/add-locked-targets-to-pyproject-toml.py `
92+ to provide locked extra groups for our package.
93+ Including locked extra groups is why we run ` scripts/add-locked-targets-to-pyproject-toml.py `
9694before any step related to building the package in the CI.
9795
9896## Read the Docs
0 commit comments