chore: GCDS Components Release

[sre-read-write]

🤖 I have created a release beep boop

gcds-components: 0.26.0-canary.0

0.26.0-canary.0 (2024-08-21)

Bug Fixes

• Margin and spacing issues in gcds-card (#617) (2d39bdc)

gcds-components-angular: 0.26.0-canary.0

0.26.0-canary.0 (2024-08-21)

Patch

• gcds-components-angular: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • peerDependencies
    • @cdssnc/gcds-components bumped from ^0.25.0 to ^0.26.0-canary.0

gcds-components-react: 0.26.0-canary.0

0.26.0-canary.0 (2024-08-21)

Patch

• gcds-components-react: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.25.0 to ^0.26.0-canary.0

gcds-components-react-ssr: 0.26.0-canary.0

0.26.0-canary.0 (2024-08-21)

New Features

• Add gcds-date-input component (#607) (ce0b4cc)
• add react ssr package (#587) (bf3fd1e)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.25.0 to ^0.26.0-canary.0

gcds-components-vue: 0.26.0-canary.0

0.26.0-canary.0 (2024-08-21)

Patch

• gcds-components-vue: Synchronize GCDS Components versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @cdssnc/gcds-components bumped from ^0.25.0 to ^0.26.0-canary.0

---

This PR was generated with Release Please. See documentation.

[ethanWallace]

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.

Reminder
🎈We have to use conventional commits in the title of our PR for release-please to pickup the commits