Hunor Csomortáni

Could "reading the changelog entry from a file" be implemented as adding (or replacing) the `changelog-entry` action on the fly? This way there would be no need for the API...

Yep, that's what I meant. But now that I think about it, it would be a little bit hackish, indeed.

Hey @sopos :wave: @lbarcziova mentioned yesterday in chat that this seems to be similar to #1355, and one workaround could be to follow the proposal made by @lachmanfrantisek in [this...

@sopos did you try using `create-archive` to achieve this? Would that work for you?

@lachmanfrantisek @TomasTomecek I moved this to be refined, so that the monorepo work can progress. I've prioritized so that it's after any card that it's about some urgent bug or...

I can confirm that downgrading grpcio to 1.57.0 stops the leak. ``` dagster==1.5.14 dagster-aws==0.21.14 dagster-azure==0.21.14 dagster-celery==0.21.14 dagster-celery-k8s==0.21.14 dagster-gcp==0.21.14 dagster-graphql==1.5.14 dagster-k8s==0.21.14 dagster-pandas==0.21.14 dagster-pipes==1.5.14 dagster-postgres==0.21.14 dagster-webserver==1.5.14 grpcio==1.57.0 grpcio-health-checking==1.57.0 ``` We also did...

@majamassarini let me know if I can help with this. We can have a call to discuss it if you want :)

This was closed in error.

Thanks for filing this issue @LecrisUT! We discussed [something like this](https://github.com/fedora-copr/copr/pull/2591#discussion_r1146193977) already, the proposal there was to use something like `after` or `build_after` in order to define the build order,...

> * Implement elsewhere -- e.g. via dashboard I think this would be the most straightforward from a user experience point of view. And this is how I've seen it...