v1.56.6

Bump pipeline version and add custom warning formatting (#385)

The latest pipeline version introduces some warnings if a project.yaml
is not using the latest version, or if it contains an action with the
reserved "run_all" action name.
See https://github.com/opensafely-core/pipeline/pull/455

These warnings all start with "ProjectWarning:" and are expected to be
printed to the console when a user runs `opensafely run`; any info other
than the message itself (e.g. the line of code that produced it, the
warning class etc) are
likely to be useless and confusing to users, so we just format them to
display the message only. Other types of warning will continue to use
the standard formatting.

Means that instead of output like:
```
➤ opensafely run run_all
/home/becky/bennett/opensafely-cli/opensafely/_vendor/pipeline/main.py:28: UserWarning: ProjectWarning: Your project file is using an old version (4.0); consider updating to version 5
  return Pipeline.build(**parsed_data)
/home/becky/bennett/opensafely-cli/opensafely/_vendor/pipeline/main.py:28: UserWarning: ProjectWarning: `run_all` is a reserved action name; user-defined actions with this name are ignored and will raise an error in later versions.
  return Pipeline.build(**parsed_data)
=> All actions already completed successfully
   Use -f option to force everything to re-run
```

We get: 
```
➤ opensafely run run_all
ProjectWarning: Your project file is using an old version (4.0); consider updating to version 5
ProjectWarning: `run_all` is a reserved action name; user-defined actions with this name are ignored and will raise an error in later versions.
=> All actions already completed successfully
   Use -f option to force everything to re-run
```

Also adds pytest config to ignore the pipeline warnings (and a driveby
fix for missing marker registration, to silence the pytest unknown
marker warnings)

v1.56.5

fix: empty commit to trigger release (#387)

v1.56.4

Better error messages for unhandled exceptions in local runs (#384)

Remove the misleading message that tech support has been contacted (it
hasn't). Print the exception traceback so the user can copy/paste it
when contact tech support, and a better user error message.

Closes #347

v1.56.3

Bump pipeline version (#378)

This pulls in the change here:
 * https://github.com/opensafely-core/pipeline/pull/446

v1.56.2

fix: actually test on python different versions in CI :facepalm: (#368)

Originally, this was attempting to fix breakage introduced by moving to
`just build` in the publishing workflow, but fixing that uncovered that
we a) were defaulting to 3.10 in dev rather than our minimum version,
3.8 and b) we were actually always testing on 3.10 on linux in CI, not
the matrix python version.

This was an unintended side effect of this change:
https://github.com/opensafely-core/opensafely-cli/commit/4412a99849ef955aeeb25198618fde183279fd7f

Moving from running `python -m pytest` to `just test` meant that we
needed to specify PYTHON_VERSION env var to specify the version of
python we are using, as we are using the just file's virtualenv
machinery.

This is a `fix:` tagged release, rather than `chore:`, because it also
(hopefully) fixes the release machinery which was broken for similar
moving from direct python to just.

v1.55.1

fix: Default to BindMountVolumeAPI on linux. (#365)

The bind mount API is faster and cleaner.

Also, github changed something about codespaces docker set up, and its
completely broken the BindMountVolumeAPI - `docker exec` doesn't work
reliably.

So, currently, all new codespaces are broken. This change fixes that, by
doing something that we should have done already.

v1.55.0

Remove `check` command (#364)

This is now superseded by the ehrQL permissions system:
 * https://github.com/opensafely-core/ehrql/pull/2543

Note that this PR should not be merged until the related
`research-action` PR has been merged, which removes the one usage of the
`opensafely check` command:
 * https://github.com/opensafely-core/research-action/pull/115

Note that we deliberately leave the `repository_permissions.yaml` file
in place to avoid triggering errors on clients which haven't yet updated
and are still trying to fetch this file. I've set a reminder to remove
this file in a couple of weeks.

v1.54.3

Merge pull request #341 from opensafely-core/Jongmassey/force-user-ag…

v1.54.2

Merge pull request #337 from opensafely-core/Jongmassey/set-user-agent

Custom UA for contacting opencodelists.org

v1.54.1

fix: Merge pull request #328 from opensafely-core/rstudio-download

fix: ensure rstudio/python images exist before running launch command