-
Notifications
You must be signed in to change notification settings - Fork 246
Insights: ClosureTree/closure_tree
Overview
-
0 Active issues
-
- 10 Merged pull requests
- 0 Open pull requests
- 0 Closed issues
- 0 New issues
Could not load contribution data
Please try again later
3 Releases published by 1 person
-
closure_tree/v9.0.0 closure_tree: v9.0.0
published
Jul 21, 2025 -
closure_tree/v9.1.0 closure_tree: v9.1.0
published
Jul 23, 2025 -
closure_tree/v9.1.1 closure_tree: v9.1.1
published
Jul 24, 2025
10 Pull requests merged by 3 people
-
Document
alias level depth
in README#461 merged
Jul 25, 2025 -
chore(master): release closure_tree 9.1.1
#460 merged
Jul 24, 2025 -
fix: restore proper deprecation for database_less configuration
#459 merged
Jul 24, 2025 -
chore(master): release closure_tree 9.1.0
#458 merged
Jul 23, 2025 -
feat: migrate from ActiveSupport::Autoload to Zeitwerk
#457 merged
Jul 23, 2025 -
chore(master): release closure_tree 9.0.0
#456 merged
Jul 21, 2025 -
fix: configure release-please to recognize v8.0.0 release
#455 merged
Jul 21, 2025 -
feat: Add runtime advisory lock name customization and multi-database…
#454 merged
Jul 21, 2025 -
Convert SQL queries to Arel where feasible
#453 merged
Jul 21, 2025 -
feat: rewrite with clean api
#451 merged
Jul 20, 2025
1 Unresolved conversation
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Fix ambiguous ORDER BY clauses by fully qualifying column names
#452 commented on
Jul 21, 2025 • 0 new comments