chore(master): release closure_tree 9.6.0

[github-actions]

🤖 I have created a release beep boop

9.6.0 (2026-02-16)

Features

• raise error when advisory lock cannot be acquired within configured timeout (#480) (c030385)
• sibling reordering when node changes parent or scope (#484) (254ba36)

---

This PR was generated with Release Please. See documentation.

[github-actions]

🤖 Created releases:

• closure_tree/v9.6.0

🌻

[sampatbadhe]

@seuros v9.6.0 is tagged but not available on RubyGems. Any plans to publish it?

[seuros]

@sampatbadhe: I push and merge.. publishing ... that a premium service... Will cost you 847$.

Link for payment

[sampatbadhe]

@seuros Thanks for the clarification.

I realize my earlier comment may have sounded like a request to publish, that wasn’t my intention. I was just trying to understand why v9.6.0 was tagged but not available like 9.5.0.

Thanks for pushing 9.6.0, I’m able to use it now.

Appreciate the work you put into maintaining the gem.

[seuros]

I was joking. 🙂

I’am being extra careful testing the gem in this org before releasing because of the lock behavior.

A normal bug crashes loudly. You notice it and fix it.

A lock bug doesnt crash. It just freezes the system quietly.

That's worse when it happen in a background job that must refresh taxonomy for example.

This gem runs inside critical infrastructure( hospitals, government systems, transport, logistics). And many teams upgrade with minimal testing.

I rather delay a release than wake up to our names featured in The Register because we rushed it.