Craig Alexander

> Note: `kramdown` is a transitive _development_ dependency by way of `logstash-devutils`, and is not included in distributed packages. Does that mean that even though it is in the `Gemfile.lock`...

It was working very reliably until Dec 14th at 3:17PM Eastern. After that, only a very small amount have succeeded. We send a hand full of requests per work day....

We were able to trim some things for the purposes of the comparison. Less than ideal but it looks to be working again. But its REALLY close to the timeout....

It started happening again. Here is the latest file: [current_api-1-9.json](https://github.com/bump-sh/cli/files/13881119/current_api-1-9.json)

That's very helpful information! I noticed we had some extra mime types that we don't need and those all container $ref. I removed them and it is around 20 seconds...

The same test failures that are present in the blocking checks are also failing on [master](https://ci.appveyor.com/project/Inumedia/slackapi/branch/master). How shall we proceed with getting this and the other prs merged?

Not one in particular. There are [16](https://hub.docker.com/layers/library/python/3.11.8-slim-bookworm/images/sha256-7db5778265af1aa0e4ba28cabc15cd5160257ce9732595526cc38a3dc75058da) that are high. It has been over a year since that image has been updated and it seemed like a good first first...

Changes made. I also opened up a pr to the docs: https://github.com/tubearchivist/docs/pull/64