Gatsby v5 plugin apiVersion requirement: which compatibility signal should gate a deployment?
After moving a site from Gatsby v4 to v5, the plugin ecosystem changed: plugins are expected to declare a supported apiVersion , and plugins written against the older API can fail during gatsby build or, worse, behave silently differently in a deployed build. The uncertainty is how to treat this boundary operationally. Build logs from the hosting provider te
gatsby