chore: GCDS Components Release

[sre-read-write]

🤖 I have created a release beep boop

gcds-components: 0.26.2

0.26.2 (2024-09-18)

🐛 🔧 Bug Fixes

• Fix typos in tokens (#646) (4c8d850)
• gcds-sr-only: Align with WCAG technique C7 (#642) (3cbe8bc)

gcds-components-angular: 0.26.2

0.26.2 (2024-09-18)

Patch

• gcds-components-angular: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • peerDependencies
    • @cdssnc/gcds-components bumped from ^0.26.1 to ^0.26.2

gcds-components-react: 0.26.2

0.26.2 (2024-09-18)

Patch

• gcds-components-react: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.26.1 to ^0.26.2

gcds-components-react-ssr: 0.26.2

0.26.2 (2024-09-18)

Patch

• gcds-components-react-ssr: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.26.1 to ^0.26.2

gcds-components-vue: 0.26.2

0.26.2 (2024-09-18)

Patch

• gcds-components-vue: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.26.1 to ^0.26.2

---

This PR was generated with Release Please. See documentation.

[daine]

What we still need to do in each Release PR:

Important: Do this just before release to prevent your changes from being overridden by the release bot

• Update lerna.json to match the new release version. This is needed to trigger the publish workflow we have.
• Update the main CHANGELOG - go through the generated CHANGELOGs for each package and copy them
• Update the title of the PR to include the version if we want to
• Make sure the react-ssr package is on the correct version and is a canary version. Add -canary.0 to its version number.