Support the class attribute for hero action link buttons

[HiDeoo]

This PR fixes an issue reported on Discord where trying to use the class attribute in hero action link buttons was not working as expected.

The link button generated with the following frontmatter would not include the TEST_CLASS_WARNING_REMOVE_ME class:

title: My Docs
template: splash
hero:
  actions:
    - text: Go
      icon: right-arrow
      link: /
      attrs:
        class: TEST_CLASS_WARNING_REMOVE_ME

[changeset-bot]

🦋 Changeset detected

Latest commit: 31b8ed3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/starlight	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for astro-starlight ready!

Name	Link
🔨 Latest commit	31b8ed3
🔍 Latest deploy log	https://app.netlify.com/sites/astro-starlight/deploys/66ce0bba2c7d8100077b1f46
😎 Deploy Preview	https://deploy-preview-2253--astro-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[delucis]

Looks good @HiDeoo — I’m curious about one detail, but happy with the code.

[delucis]

Huh, interesting! Do you know why this extra work is needed? Because Astro already sets a class and uses that instead of the one spread in from attrs? Feels like maybe something we should report to the team.

[HiDeoo]

Good question, I always assumed this was the expected pattern to use with our scopedStyleStrategy when you want to accept a class that you would pass down to a child and the component also get a scoped class. Using class would result with one being overwritten by the other so you would have to use class:list. Thinking about it, I guess this may be handled automatically, never thought about it, could be a good question to ask 🤔

[delucis]

Asked on Discord, but I think we can still make this change as a fix for now!

[delucis]

Thanks for the fix @HiDeoo!