no idea why is this failing, the change in this PR was to the release workflow logic, which was not even ran here

FAILED tests/test_example.py::test_example_repo_updates - AssertionError: You are downgrading from 2.3.0 to 2.1.0.post31.dev0+56b5bde. Downgrades are not supported.
  
assert 1 == 0
 +  where 1 = CompletedProcess(args=['copier', 'update', '--trust', '--vcs-ref=HEAD', '--data-file', '/home/runner/work/python-copier-template/python-copier-template/example-answers.yml'], returncode=1, stdout=b'You are downgrading from 2.3.0 to 2.1.0.post31.dev0+56b5bde. Downgrades are not supported.\n').returncode
 

no idea why is this failing, the change in this PR was to the release workflow logic, which was not even ran here

FAILED tests/test_example.py::test_example_repo_updates - AssertionError: You are downgrading from 2.3.0 to 2.1.0.post31.dev0+56b5bde. Downgrades are not supported.
  
assert 1 == 0
 +  where 1 = CompletedProcess(args=['copier', 'update', '--trust', '--vcs-ref=HEAD', '--data-file', '/home/runner/work/python-copier-template/python-copier-template/example-answers.yml'], returncode=1, stdout=b'You are downgrading from 2.3.0 to 2.1.0.post31.dev0+56b5bde. Downgrades are not supported.\n').returncode
 

Part of the CI updates the example repo, so you need to rebase any PRs on main. This is 39 commits behind main at the moment, which means it tries to downgrade the example repo as part of the checks

Please also provide:

• A reason why we should add this
• What prompted you to add this
• A project where it is in use and providing useful output
• Details on whether it is checking just the project requirements or also the dev extra requirements

I just added 'fixes issue'

#182

maybe I forgot about the part where it's tested in a separate project

Please add this to another project first and report back the useful information that it produced so we can review if it's worth adding

ok

DiamondLightSource/dodal#825