avo 4.1.16 → 4.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 845688c3072b859a637cd79462214f6b667dd750c608c88fa476d2809d777bfb
-  data.tar.gz: 8dffd2ea29c19a5f377b009021b103ff4b767517828eb28787cfad108306c52b
+  metadata.gz: a8fc8217917ff1df1a558c0628a15ade9d6315ebfceaa37797d86a222c33c133
+  data.tar.gz: b29348ca3dbb0631138eb904a0b94f32fbfcbe3d600a889753cd76b6f48d7081
 SHA512:
-  metadata.gz: 67bab9d6559d5b9a88781c596c287c721e7aacd283fb2c05b170f6ba021165bfcc0c5fd60e25d05fc84ef5445343dd4ef1d2b1eab546b0ae42f0e07685d3a9bd
-  data.tar.gz: 54657abfc3a1fde08ef3e52a7f129f6f40ebad886a644b5d37346958f0176e4c477d733164a2856bc2b0e5d82514fcb4ba08b8b72bb017f6c96264364cab5b21
+  metadata.gz: 2c4850f236ead8cc76af7a46a1eb72b0f63ee4b5be5db756a0c8e731064edfc5185b35471489e44174f66c261818a0e4dd813b75775ce994142a53a7abf4c8f8
+  data.tar.gz: a8b1779397837e6551fc26e2800b39e14e617c5fc25a66cfabe9b42b0d7af3c49c4047b242ca019131e67e8e627b00c038b8c8d35e38a9d374dcc56bf76c474b

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    avo (4.1.16)
+    avo (4.2.0)
       actionview (>= 6.1)
       active_link_to
       activerecord (>= 6.1)

data/lib/avo/concerns/has_items.rb

@@ -202,7 +202,44 @@ module Avo
         items_holder&.items || []
       end
 
+      # Every container asks its children whether they have anything visible, so one
+      # render may call this thousands of times and each call walks the whole subtree.
+      # Memoizing it offers a significant performance boost, particularly for large
+      # resources.
+      #
+      # It can't be a plain `||=` because the contextual items can change throughout a
+      # request lifecycle.
+      #
+      # The context is compared by object identity, so anything *replaced* recomputes.
+      # `items.size` is in there because `Holder#add_item` appends in place: a holder
+      # that gains an item keeps both its own identity and its array's, so the count is
+      # the only cheap signal that the items changed underneath us.
+      #
+      # Request-scoped state (params, context, current_user) is deliberately absent.
+      # `detect_fields` is a `before_action` and assigns a brand-new `Items::Holder`, so
+      # the memo is already cold at the top of every request and none of those can change
+      # within the lifetime of one entry.
       def visible_items
+        hydration_resource = is_a?(Avo::Resources::Base) ? self : try(:resource)
+        context = [@items_holder, items.size, view.to_s.to_sym, hydration_resource.try(:record)]
+
+        unless @visible_items_context&.zip(context)&.all? { |was, now| was.equal?(now) }
+          @visible_items_context = context
+          # Frozen because every caller now shares one array. Without it a caller that
+          # mutates the result silently corrupts every later read instead of failing.
+          @visible_items = compute_visible_items.freeze
+        end
+
+        @visible_items
+      end
+
+      def is_empty?
+        visible_items.blank?
+      end
+
+      private
+
+      def compute_visible_items
         items
           .map do |item|
             hydrate_item item
@@ -269,12 +306,6 @@ module Avo
           end.compact
       end
 
-      def is_empty?
-        visible_items.blank?
-      end
-
-      private
-
       def set_target_to_top(fields)
         fields.each do |field|
           field.target = :_top

data/lib/avo/skills/avo-update/SKILL.md

@@ -92,7 +92,7 @@ Guide sections are headed by version (`## Upgrade to 3.22.0`, `## Upgrade from 3
 
 For each section between your before and after versions:
 
-1. **Inventory first.** Grep for the API the section touches *before* changing anything. Most sections won't apply to a given app.
+1. **Inventory first.** Grep for the API the section touches *before* changing anything — and where the section is about how a label or key resolves, grep `config/locales` too, since the trigger can be a key the app already defines rather than anything in its Ruby. Most sections won't apply to a given app.
 2. Mark it **APPLIES / NOT USED / NEEDS REVIEW** in the log. Never apply a change for an API the app doesn't use.
 3. If it applies, make the edit, then boot the app and re-run the tests.
 4. Commit per section, with the version in the message.
@@ -163,6 +163,7 @@ Check the project's own instructions for how — in this order: `AGENTS.md`, `CL
 - **The update alone is not the upgrade.** Bumping the gems and skipping the guide is the single most common way an admin breaks after an "upgrade" — and the breakage often surfaces days later, in a view nobody opened.
 - **Apply sections oldest → newest.** They're written as a chain; applying 4.0.12's change before 4.0.7's can leave you editing code the earlier section was about to rename.
 - **Silent default flips pass tests.** Sections that change a default (authorization strictness, confirmation modals, expanded filters) break nothing visible in CI and change runtime behavior. Call these out individually.
+- **A section can be triggered by the app's locale files, not its Ruby.** Avo has been moving label resolution so a derived i18n key wins *over* the class attribute — actions in `4.0.17`, then cards, dashboards and scopes in `avo-dashboards` / `avo-scopes` `4.1.2`. Nothing in the app's Ruby changed, so grepping for an API name finds nothing; the trigger is a key the app already defines under `avo.action_translations`, `avo.card_translations`, `avo.dashboard_translations` or `avo.scope_translations`. Where one exists the class attribute stops being read **even when it's a lambda**, which is then never called and computes nothing, with no error. Grep those roots in `config/locales`, and move the collision with `self.translation_key` (or a value at the registration site) rather than deleting the key — **avo-i18n**.
 - **Add-on gems version independently.** `avo-kanban 0.1.17 → 0.1.18` has its own section even when Avo core barely moved. Work the lock diff, not just the core version.
 - **Assets after upgrade.** A GitHub-sourced install ships no precompiled assets — re-run `rake avo:build-assets` or the admin renders unstyled (**avo-setup**).
 - **Don't invent a migration.** If a version's change isn't in the guide or the release notes, stop and ask rather than guessing at the new API.

data/lib/avo/skills/docs-index.json

@@ -1,7 +1,7 @@
 {
   "repo": "avo-hq/docs.avohq.io",
   "docs_path": "docs/4.0",
-  "commit": "70f1de9c11258f0f376862cc87b68a0d5ea48940",
-  "date": "2026-08-20",
+  "commit": "ee0277f1883e8a01c9d20503e05aa9f26170e93e",
+  "date": "2026-08-31",
   "note": "The docs commit these skills were last indexed from. Run ruby lib/avo/skills/bin/docs_drift.rb to see what changed since, and --update after a refresh."
 }

data/lib/avo/version.rb

@@ -1,3 +1,3 @@
 module Avo
-  VERSION = "4.1.16" unless const_defined?(:VERSION)
+  VERSION = "4.2.0" unless const_defined?(:VERSION)
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: avo
 version: !ruby/object:Gem::Version
-  version: 4.1.16
+  version: 4.2.0
 platform: ruby
 authors:
 - Adrian Marin