From b8c9486e87561d34871212bee477073742daa3a7 Mon Sep 17 00:00:00 2001
From: chris-doucette-stack <cdoucette@stackoverflow.com>
Date: Thu, 12 Mar 2026 10:26:56 -0400
Subject: [PATCH 1/4] adding linkClass property

---
 .../src/components/Menu/Menu.test.ts              | 15 +++++++++++++++
 .../src/components/Menu/MenuItem.svelte           |  8 +++++++-
 2 files changed, 22 insertions(+), 1 deletion(-)

diff --git a/packages/stacks-svelte/src/components/Menu/Menu.test.ts b/packages/stacks-svelte/src/components/Menu/Menu.test.ts
index d8c12d54db..d969409237 100644
--- a/packages/stacks-svelte/src/components/Menu/Menu.test.ts
+++ b/packages/stacks-svelte/src/components/Menu/Menu.test.ts
@@ -125,6 +125,21 @@ describe("Menu", () => {
         expect(link).to.have.class("s-menu--action__danger");
     });
 
+    it("should render with arbitrary link classes", () => {
+        const menuItems = createSvelteComponentsSnippet([
+            createMenuItem({
+                href: "#",
+                linkClass: "custom-link-class",
+                children: children("Delete"),
+            }),
+        ]);
+
+        render(Menu, { children: menuItems });
+
+        const link =screen.getByRole("menuitem").querySelector("a");
+        expect(link).to.have.class("custom-link-class");
+    });
+
     // Menu Check Item
     it("should render menu check item with required props", () => {
         const menuCheckItems = createSvelteComponentsSnippet([
diff --git a/packages/stacks-svelte/src/components/Menu/MenuItem.svelte b/packages/stacks-svelte/src/components/Menu/MenuItem.svelte
index 39bfc0856b..e10b10fe4a 100644
--- a/packages/stacks-svelte/src/components/Menu/MenuItem.svelte
+++ b/packages/stacks-svelte/src/components/Menu/MenuItem.svelte
@@ -39,6 +39,11 @@
          */
         class?: string;
 
+        /**
+         * Additional CSS classes added to the link element
+         */
+        linkClass?: string;
+
         /**
          * Snippet for the menu item content
          */
@@ -51,6 +56,7 @@
         icon,
         selected = false,
         class: className = "",
+        linkClass = "",
         onclick,
         children,
         ...restProps
@@ -84,7 +90,7 @@
     };
 
     const itemClasses = $derived(getItemClasses(className));
-    const linkClasses = $derived(getLinkClasses("", danger, selected));
+    const linkClasses = $derived(getLinkClasses(linkClass, danger, selected));
 </script>
 
 <li class={itemClasses} role="menuitem">

From e73311f8a2f8b5b3eebf88e242ed30aa55a56ca2 Mon Sep 17 00:00:00 2001
From: chris-doucette-stack <cdoucette@stackoverflow.com>
Date: Thu, 12 Mar 2026 10:40:39 -0400
Subject: [PATCH 2/4] lint fix

---
 packages/stacks-svelte/src/components/Menu/Menu.test.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/stacks-svelte/src/components/Menu/Menu.test.ts b/packages/stacks-svelte/src/components/Menu/Menu.test.ts
index d969409237..3f1bf336b3 100644
--- a/packages/stacks-svelte/src/components/Menu/Menu.test.ts
+++ b/packages/stacks-svelte/src/components/Menu/Menu.test.ts
@@ -136,7 +136,7 @@ describe("Menu", () => {
 
         render(Menu, { children: menuItems });
 
-        const link =screen.getByRole("menuitem").querySelector("a");
+        const link = screen.getByRole("menuitem").querySelector("a");
         expect(link).to.have.class("custom-link-class");
     });
 

From b07661658dad8f65f8576f1e732adc8bb5e70636 Mon Sep 17 00:00:00 2001
From: chris-doucette-stack <cdoucette@stackoverflow.com>
Date: Thu, 12 Mar 2026 10:45:39 -0400
Subject: [PATCH 3/4] add changeset

---
 .changeset/cuddly-moons-rule.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 .changeset/cuddly-moons-rule.md

diff --git a/.changeset/cuddly-moons-rule.md b/.changeset/cuddly-moons-rule.md
new file mode 100644
index 0000000000..321153fb02
--- /dev/null
+++ b/.changeset/cuddly-moons-rule.md
@@ -0,0 +1,5 @@
+---
+"@stackoverflow/stacks-svelte": minor
+---
+
+Added linkClass css property to MenuItem

From 7827489769f06114fbb6681032dc099d987b60e2 Mon Sep 17 00:00:00 2001
From: chris-doucette-stack <cdoucette@stackoverflow.com>
Date: Thu, 12 Mar 2026 10:47:33 -0400
Subject: [PATCH 4/4] fix typo in ReadMe

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fd34690e09..956ed2d64a 100755
--- a/README.md
+++ b/README.md
@@ -179,7 +179,7 @@ This repo uses [Semantic Versioning](https://semver.org/) to distribute Stacks C
 
 We use [changesets](https://github.com/changesets/changesets) to automatize the steps necessary to publish to NPM, create GH releases and a changelog.
 
-- Every time you do work that requires a new release to be published, [add a changesets entry](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md) by running `npx chageset` and follow the instructions on screen. (changes that do not require a new release - e.g. changing a test file - don’t need a changeset).
+- Every time you do work that requires a new release to be published, [add a changesets entry](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md) by running `npx changeset` and follow the instructions on screen. (changes that do not require a new release - e.g. changing a test file - don’t need a changeset).
     - When opening a PR without a corresponding changeset the [changesets-bot](https://github.com/apps/changeset-bot) will remind you to do so. It generally makes sense to have one changeset for PR (if the PR changes do not require a new release to be published the bot message can be safely ignored)
 - The [release github workflow](.github/workflows/release.yml) continuosly check if there are new pending changesets in the main branch, if there are it creates a GH PR (`chore(release)` [see example](https://github.com/StackExchange/apca-check/pull/2)) and continue updating it as more changesets are potentially pushed/merged to the main branch.
 - When we are ready to cut a release we need to simply merge the `chore(release)` PR back to main and the release github workflow will take care of publishing the changes to NPM and create a GH release for us. The `chore(release)` PR also give us an opportunity to adjust the automatically generated changelog when necessary (the entry in the changelog file is also what will end up in the GH release notes).