Cassie Coyle
Cassie Coyle
I'll close it and ensure everything noted above, but not done is put in my [Scheduler Stable issue](https://github.com/dapr/dapr/issues/7796) if it makes sense or a new/diff issue if that makes more...
> > Great start @pglushko - thanks for keeping the error codes the same for backwards compatibility 🙂 Next will be writing the integration tests. I don't see a secrets...
gentle ping @pglushko
[linking to release 1.13](https://github.com/dapr/dapr/issues/7093)
I added the `pinned` label so it shouldn't go `stale` again. We should continue to ease the experience of developers contributing to the project :)
Should this be reopened? cc @artursouza
@RyanLettieri this would be great to have in next release if possible :)
@sadath-12 gentle ping on this PR :)
> Hi @cicoyle, I'd appreciate early feedback to ensure I'm on the right track. I've implemented new lock error models, replaced existing errors with them, and fixed unit tests. >...
Gentle ping @moonorange - unfortunately I do not believe we will get this change in this release, but if you have the bandwidth to wrap up the components-contrib changes we...