chore: update @github/relative-time-element to 5.0.0

[Copilot]

Updates @github/relative-time-element from ^4.5.0 to ^5.0.0.

Breaking changes in v5.0.0: The only change is the removal of JSX IntrinsicElements type augmentation for <relative-time> (PR #335). This does not affect @primer/react because:

• The RelativeTime component uses createComponent from @lit-labs/react, exposing a proper React component
• Consumers use <RelativeTime>, not <relative-time> directly
• The removed JSX types were never part of @primer/react's public API

All builds, tests, and type checks pass without any code changes.

Changelog

New

Changed

• Updated @github/relative-time-element from ^4.5.0 to ^5.0.0

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

The versioning guide indicates that bumping a dependency to a newer major version warrants a major bump. However, the breaking change in v5.0.0 (removal of JSX IntrinsicElements augmentation) does not affect @primer/react's public API since the RelativeTime component uses a createComponent wrapper. A minor bump is appropriate here. Please review and adjust if you disagree.

Testing & Reviewing

No code changes required — only a dependency version bump. Verified by:

• ✅ npm run build succeeds
• ✅ npm test passes (all unit tests)
• ✅ npm run type-check passes (all packages)

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github-ui (Learn more about how to run integration tests)

[github-actions]

⚠️ Action required

👋 Hi, this pull request contains changes to the source code that github/github-ui depends on. If you are GitHub staff, test these changes with github/github-ui using the integration workflow. Check the integration testing docs for step-by-step instructions. Or, apply the integration-tests: skipped manually label to skip these checks.

To publish a canary release for integration testing, apply the Canary Release label to this PR.

[Copilot]

Pull request overview

Updates @github/relative-time-element to v5 in @primer/react and refreshes the lockfile accordingly.

Changes:

• Bumped @github/relative-time-element from ^4.5.0 to ^5.0.0 in packages/react.
• Updated package-lock.json to reflect the new dependency version and associated lockfile metadata updates.

Show a summary per file

File	Description
packages/react/package.json	Updates @github/relative-time-element dependency range to ^5.0.0.
package-lock.json	Updates the resolved @github/relative-time-element package to 5.0.0 and refreshes lockfile entries impacted by the install.

Copilot's findings

• Files reviewed: 1/2 changed files
• Comments generated: 1

[Copilot]

Upgrading to @github/relative-time-element v5 removes the package’s JSX IntrinsicElements augmentation. Since @primer/react imports this dependency (e.g. RelativeTimeElement), that augmentation could previously have been visible to TS consumers and enabled using <relative-time> directly in TSX without extra declarations. Please confirm whether this is considered a breaking change for @primer/react consumers (and whether a major bump / explicit migration note is needed) even if the documented API is the RelativeTime React wrapper.

Suggested change

	"@github/relative-time-element": "^5.0.0",
	"@github/relative-time-element": "^4.0.0",

[francinelucca]

FYI #7656 (comment)

[siddharthkp]

FYI #7656 (comment),

Copilot:
Per contributor-docs/versioning.md, increasing a dependency to a newer major version should be treated as a major semver bump for @primer/react

Also, copilot:

The versioning guide indicates that bumping a dependency to a newer major version warrants a major bump. However, the breaking change in v5.0.0 (removal of JSX IntrinsicElements augmentation) does not affect @primer/react's public API since the RelativeTime component uses a createComponent wrapper. A minor bump is appropriate here.

The guidance in versioning.md seems a bit too strict without any nuance? I'm inclined to agree with 2nd copilot, it's only a breaking change for primer/react if there is something that breaks for primer/react 🤔

I realise this rule exists because someone might be consuming the transitive dependency that comes with primer/react in their application in a way that breaks. But that's not the case for dotcom at least because they already override the dependency to use 5.0.0 and not the version in primer/react

[primer-integration]

👋 Hi from github/github-ui! Your integration PR is ready: https://github.com/github/github-ui/pull/18319

[primer-integration]

Integration test results from github/github-ui:

  CI Passed
  VRT Passed
  Projects Passed

All checks passed!