@sebgroup/green-core 3.5.0 → 3.5.1

package/gds-element.js

@@ -16,7 +16,7 @@ class GdsElement extends LitElement {
     /**
      * The semantic version of this element. Can be used for troubleshooting to verify the version being used.
      */
-    this.semanticVersion = "3.5.0";
+    this.semanticVersion = "3.5.1";
     this.syncFirstRender = false;
     this._isUsingTransitionalStyles = false;
     this._dynamicStylesController = new DynamicStylesController(this);

package/generated/mcp/components.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-10T07:14:04.624Z",
+  "generatedAt": "2026-04-24T13:51:13.604Z",
   "components": [
     {
       "name": "gds-alert",

package/generated/mcp/form-summary/guidelines.md

@@ -9,11 +9,15 @@ Form summary shows all form errors in one place.
 
 Form summary works automatically when placed in a form with form controls from Green Core. It has two update modes, `default` and `reactive`. In the default mode, a `refresh()` method needs to be called for the component to update and reflect the current state of the form. In the `reactive` mode, it will update on the fly as soon as the status of a control in the form changes. The `reactive` mode requires less setup to use, but the `default` mode allows for more control over the behavior.
 
-#### Accessibility
+#### Fieldset labels
+
+To reflect the structure of the form, the summary content can be grouped using fieldset labels. These act as headings for related fields and help users quickly understand how the information is organized. By mirroring the same grouping as in the form, it becomes easier to recognize and review the content, improving both clarity and confidence before submission.
+
+### Accessibility
 
 Semantically, the form summary is represented as a navigation region containing an unordered list of links.
 
-#### Compatibility
+### Compatibility
 
 Form summary is mainly intended for use with form controls from Green Core, but it also works with generic native form controls by using data-attributes.
 

package/generated/mcp/icons.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-10T07:14:04.624Z",
+  "generatedAt": "2026-04-24T13:51:13.604Z",
   "icons": [
     {
       "name": "gds-icon-ai",

package/generated/mcp/index.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-10T07:14:04.624Z",
+  "generatedAt": "2026-04-24T13:51:13.604Z",
   "instructions": "./INSTRUCTIONS.md",
   "components": "./components.json",
   "icons": "./icons.json",

package/generated/mcp/pagination/guidelines.md

@@ -1,14 +1,24 @@
 # Pagination
 
-Pagination helps users navigate large result sets by dividing content into clear, manageable pages.
+Pagination helps users navigate large result sets by dividing content into clear, manageable pages. 
 
 
 ## Overview
 
 ### Usage
 
-*   Use pagination for long lists such as tables, search results, or content listings.
-    
-*   Pagination is preferred over infinite scroll when users need overview, comparison, or predictable navigation.
-    
-*   Always associate pagination with the content it controls.
+Pagination is used to divide large amounts of content into smaller pages, making it easier to navigate and understand a dataset. It is most useful when content cannot be displayed at once, or when users need to move through information in a defined order.
+
+Use pagination when it improves readability and control, for example in tables or long lists, search results, or content listings. Avoid using pagination for small datasets or when continuous scrolling provides a better experience.
+
+
+
+### Behaviour
+
+Pagination should clearly indicate the current page and keep navigation consistent and predictable. Unavailable actions should be disabled at the start or end of the page range. When used with data tables, the item range and total number of items should be displayed.
+
+### Accessibility
+
+Pagination should use a semantic navigation structure and ensure that all controls are keyboard accessible. The current page should be communicated programmatically, and visual styling alone should not be relied on to convey state.
+
+### Do's and don'ts

package/generated/mcp/tokens.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-04-10T07:14:04.518Z",
+  "generatedAt": "2026-04-24T13:51:12.719Z",
   "categories": {
     "space": {
       "description": "Spacing tokens for padding, margin, gap, and other spacing",

package/generated/react/index.d.ts

@@ -1,6 +1,6 @@
 export * from './alert/index.js';
-export * from './badge/index.js';
 export * from './blur/index.js';
+export * from './badge/index.js';
 export * from './breadcrumbs/index.js';
 export * from './button/index.js';
 export * from './calendar/index.js';

package/generated/react/index.js

@@ -1,6 +1,6 @@
 export * from "./alert/index.js";
-export * from "./badge/index.js";
 export * from "./blur/index.js";
+export * from "./badge/index.js";
 export * from "./breadcrumbs/index.js";
 export * from "./button/index.js";
 export * from "./calendar/index.js";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sebgroup/green-core",
   "description": "A carefully crafted set of Web Components, laying the foundation of the Green Design System.",
-  "version": "3.5.0",
+  "version": "3.5.1",
   "main": "index.js",
   "module": "index.js",
   "type": "module",

package/utils/helpers/custom-element-scoping.js

@@ -1,6 +1,6 @@
 import "../../chunks/chunk.CAV4X6PU.js";
 import { html as litHtml } from "lit";
-const VER_SUFFIX = "-dfb7e4";
+const VER_SUFFIX = "-3228cb";
 class ScopedElementRegistry {
   static get instance() {
     if (!globalThis.__gdsElementLookupTable?.[VER_SUFFIX])