Skip to content

fix(core): rename user agent file to match convention#2598

Merged
matthewvolk merged 1 commit intocanaryfrom
fix/rename-user-agent
Sep 9, 2025
Merged

fix(core): rename user agent file to match convention#2598
matthewvolk merged 1 commit intocanaryfrom
fix/rename-user-agent

Conversation

@matthewvolk
Copy link
Copy Markdown
Contributor

@matthewvolk matthewvolk commented Sep 9, 2025

What/Why?

This pull request renames the userAgent.ts file to user-agent.ts to follow the project's naming conventions for kebab-case file names. The file was previously using camelCase naming which is inconsistent with other files in the codebase.

Testing

  • Verified that the import still works correctly after the rename
  • Confirmed no other files reference the old file name
  • Ensured the build process continues to work with the new file name

Migration

No migration needed - this is a simple file rename with updated import. Developers should be aware that any direct references to the old file name will need to be updated.

Jira: CATALYST-1477

@matthewvolk matthewvolk requested a review from a team September 9, 2025 15:53
@vercel
Copy link
Copy Markdown

vercel Bot commented Sep 9, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
catalyst-b2b Ready Ready Preview Comment Sep 9, 2025 3:55pm
catalyst-canary Ready Ready Preview Comment Sep 9, 2025 3:55pm
3 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
catalyst Ignored Ignored Sep 9, 2025 3:55pm
catalyst-au Ignored Ignored Sep 9, 2025 3:55pm
catalyst-uk Ignored Ignored Sep 9, 2025 3:55pm

@matthewvolk matthewvolk added this pull request to the merge queue Sep 9, 2025
Merged via the queue into canary with commit ceb6455 Sep 9, 2025
14 checks passed
@matthewvolk matthewvolk deleted the fix/rename-user-agent branch September 9, 2025 15:56
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Sep 9, 2025

⚠️ No Changeset found

Latest commit: 1a27bb9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants