Merge branch 'master' into finalize-docs

Author: Radonirinaunimi

.github/actions/cache-test-data/action.yml

@@ -10,10 +10,11 @@ runs:
       uses: actions/cache@v4
       with:
         path: test-data
-        key: test-data-v24
+        key: test-data-v30
     - name: Download test data if cache miss
       if: steps.cache.outputs.cache-hit != 'true'
       run: |
         cd maintainer
+        # TODO: if this script fails to download some files, the cache is saved nevertheless
         ./download-test-data.sh
       shell: bash

.github/workflows/release-wheels.yaml

@@ -50,7 +50,7 @@ jobs:
         uses: PyO3/maturin-action@v1
         with:
           target: ${{ matrix.platform.target }}
-          args: --release --out dist --interpreter python3.8 python3.9 python3.10 python3.11 python3.12 python3.13 python3.14 pypy3.9 pypy3.10 pypy3.11 --manifest-path pineappl_py/Cargo.toml
+          args: --release --out dist --interpreter python3.8 python3.9 python3.10 python3.11 python3.12 python3.13 python3.14 pypy3.11 --manifest-path pineappl_py/Cargo.toml
           sccache: ${{ !startsWith(github.ref, 'refs/tags/') }}
           manylinux: ${{ matrix.platform.manylinux }}
       - name: Upload wheels
@@ -143,7 +143,7 @@ jobs:
         uses: PyO3/maturin-action@v1
         with:
           target: ${{ matrix.platform.target }}
-          args: --release --out dist --interpreter python3.7 python3.8 python3.9 python3.10 python3.11 python3.12 python3.13 python3.14 pypy3.9 pypy3.10 --manifest-path pineappl_py/Cargo.toml
+          args: --release --out dist --interpreter python3.7 python3.8 python3.9 python3.10 python3.11 python3.12 python3.13 python3.14 --manifest-path pineappl_py/Cargo.toml
           sccache: ${{ !startsWith(github.ref, 'refs/tags/') }}
       - name: Upload wheels
         uses: actions/upload-artifact@v5

CHANGELOG.md

@@ -11,11 +11,14 @@ Starting with this version, PineAPPL has an official logo!
 
 ### Added
 
+- added `optimize_using` in `Grid` objects of the Python API
 - added an actual implementation of `pineappl_grid_metadata` and
   `pineappl_grid_set_metadata` in the APIs
 
 ### Fixed
 
+- fixed fragmentation scale evolution, particularly for the specific case where
+  the fragmentation scale is the only scale present
 - fixed a bug in the Newton's convergence method by raising the maximum number
   of iteration
 - fixed a bug in the implementation of `pineappl_channels_add` of the Fortran
@@ -26,6 +29,9 @@ Starting with this version, PineAPPL has an official logo!
 
 - raised MSRV to 1.94.0
 - raised Rust edition to 2024
+- instead of depending on a previous version of the PineAPPL crate, a new crate
+  `pineappl_v0` is now responsible for loading files with file version `v0`
+- raised dependency on `pyo3` to 0.27, which drops support for PyPy 3.9 and 3.10
 
 ## [1.3.3] - 01/03/2026
 

CONTRIBUTING.md

@@ -7,9 +7,6 @@
   it compiles properly. Also, check if your changes introduce any new linter
   warnings by running `cargo clippy`.
 - Make sure to keep `CHANGELOG.md` up-to-date.
-- Make sure not to use Rust features newer than the specified minimum supported
-  Rust Version (MSRV), which is documented in the [README](README.md). You can
-  use `cargo-msrv` to check the crates. However, the Github CI also checks this.
 - Make sure to follow the [Rust API Guidelines]
 
 [Rust API Guidelines]: https://rust-lang.github.io/api-guidelines/checklist.html
@@ -19,17 +16,17 @@
 Do not change the MSRV for releases with increased patch version number. When
 increasing the MSRV make sure to set it everywhere to the same value:
 
-1. first update the `pineappl-ci` container, by
+1. first update the container file `maintainer/Containerfile`, by
    - adding the new MSRV to the variable `RUST_V`,
    - making sure the nightly version is the last entry and
    - leaving in the previous MSRV to not break the CI in between the transition
      from it
-2. commit the previous changes and manually run the `Container` Github action
+   - removing the oldest stable version
+2. commit the previous changes and manually run the `Container` GitHub action
 3. next, update the MSRV in the following files:
    - in the top-level `Cargo.toml`; all other projects in the workspace should
      inherit the setting in their respective `Cargo.toml` files
    - in `README.md` and `docs/installation.md`
-   - in all Github workflows (`.github/workflows/`)
    - in `.readthedocs.yml` update the value of the `rust` field and make sure
      [RTD supports it](https://docs.readthedocs.io/en/stable/config-file/v2.html#build-tools-rust)
 4. commit the previous changes and push them *after* the container created by
@@ -51,26 +48,32 @@ increasing the MSRV make sure to set it everywhere to the same value:
 - if you write a test that needs test data (grids, EKOs, etc.) store them at
   <https://data.nnpdf.science/pineappl/test-data/>. Ask one of the maintainers
   to upload the data for you if you don't have access to this location. Then
-  add a line to `maintainer/generate-coverage.sh` that downloads the data with
-  `wget` and a similar line to `.github/workflows/rust.yml` that downloads the
-  data with `curl`. To make Github refresh the cached test data when running
-  the CI, increase the integer `XX` in the line `key: test-data-vXX` by one.
+  add a line to `maintainer/download-test-data.sh` that downloads the files and
+  increase the version integer `test-data-vXX` in
+  `.github/actions/cache-test-data/action.yml`. To make GitHub refresh the
+  cached test data when running the CI, increase the integer `XX` in the line
+  `key: test-data-vXX` by one.
+
+### Regression tests for GitHub Issues
+
+If you're writing a regression test for a GitHub Issue, name the test
+`issue_XXX`, where `XXX` is the GitHub Issue number.
 
 ## Git
 
 - When you commit, make sure the commit message is written properly. This
   blogpost explains it nicely: <https://chris.beams.io/posts/git-commit/>.
 - Whenever you have unpushed local commits that are behind `origin/master`, use
   `git pull --rebase` to rebase them
-- When editing Github workflow files, use a separate branch, because usually
+- When editing GitHub workflow files, use a separate branch, because usually
   many commits are needed to get something working. When merging this branch
   into `master` (or any other branch), squash-merge the commits; the exact
   history in this case is not important
 
 ## Making a new release
 
 First make sure the release workflow works; since we've hard-coded runner image
-and action versions, it's possible that the workflow must be updated if these
+and action versions, it's possible that some workflows must be updated if these
 images don't exist anymore. To check whether that's the case, manually trigger
 the following workflows:
 
@@ -96,11 +99,11 @@ generated, for which the pull request will have to be accepted manually though.
 
 ## Updating the CI's container
 
-To update the software the CI runs with, modify the files in
-`maintainer/pineappl-ci`. See `maintainer/README.md` for a description of what
-these files do. To generate a new container, you need to manually run the
-[Container action] from the branch in which you modified the container files.
-After the container has been generated, all following commits in *every* branch
-will use the new container.
+To update the software the CI runs with, modify `maintainer/Containerfile`
+`maintainer/build-container.sh`. See also `maintainer/README.md` for a
+description of what these files do. To generate a new container, you need to
+manually run the [Container action] from the branch in which you modified the
+container files. After the container has been generated, all following commits
+in *every* branch will use the new container.
 
 [Container action]: https://github.com/NNPDF/pineappl/actions/workflows/container.yml