agnesgaroux

- ~~Committing and pushing auto-formatting changes ([example](https://github.com/wellcomecollection/catalogue-pipeline/blob/main/.buildkite/scripts/push_autoformatting_changes.sh), equivalent scripts exist on most repos).~~ - Updating changelogs and pushing release tags ([example](https://github.com/wellcomecollection/scala-libs/blob/main/.buildkite/scripts/release.py), equivalents exist for other versioned repos eg terraform modules)....

Done and sent, waiting for VS to get back to me

See [HOTFIX: snapshot reporter catalogue-api#874](https://github.com/wellcomecollection/catalogue-api/pull/874) for where to get the pipeline date now

BLOCKED: waiting for the records to be suppressed in Sierra

Isn't node 22 the highest available for lambdas https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

Will need to upgrade terraform in cache/terraform.tf ``` terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 5.0" // to support new node runtime } }...

Sensible to wait for 24 to become LTS if it's happening soon!

There's a python code snippet [here](https://github.com/wellcomecollection/platform/issues/5810) that checks every AWS account for lambdas where the runtime starts with `nodejs` then print the account name, fn name and runtime version

## Requirements - GET requesting status for an item, ie. can it be requested at all, ever? This is recorded by the catalogue-pipeline and makes it so that the catalogue-api...

Axiell Collections web api doesn't expose /patron, /items or /hold endpoints like the ones we use in Sierra to perform operations related to patrons and items requesting However we have...