Skip to content

chore: Update to dot com#2155

Merged
perkinsjr merged 2 commits intomainfrom
update-email-address
Oct 2, 2024
Merged

chore: Update to dot com#2155
perkinsjr merged 2 commits intomainfrom
update-email-address

Conversation

@perkinsjr
Copy link
Member

@perkinsjr perkinsjr commented Oct 2, 2024

We has dot com, we should use it.

What does this PR do?

Fixes # (issue)

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps use understand why this PR exists

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

Summary by CodeRabbit

  • Bug Fixes
    • Updated the email address used for sending notifications to ensure proper delivery.
    • Affected notifications include trial end, subscription end, welcome emails, payment issues, and leaked key alerts.

We has dot com, we should use it.
@perkinsjr perkinsjr requested a review from chronark as a code owner October 2, 2024 18:29
@changeset-bot
Copy link

changeset-bot bot commented Oct 2, 2024

⚠️ No Changeset found

Latest commit: 79af809

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@vercel
Copy link

vercel bot commented Oct 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2024 6:38pm
planetfall 🛑 Canceled (Inspect) Oct 2, 2024 6:38pm
play 🛑 Canceled (Inspect) Oct 2, 2024 6:38pm
workflows ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2024 6:38pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 2, 2024 6:38pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 2, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request focus on updating the from email address in the Resend class located in internal/resend/src/client.tsx. The email address has been changed from "james@updates.unkey.dev" to "james@updates.unkey.com" across several methods responsible for sending various types of emails. The core functionality and structure of these methods remain intact, ensuring they continue to process requests and handle errors as before.

Changes

File Path Change Summary
internal/resend/src/client.tsx Updated from email address in methods: sendTrialEnded, sendSubscriptionEnded, sendWelcomeEmail, sendPaymentIssue, sendLeakedKeyEmail from "james@updates.unkey.dev" to "james@updates.unkey.com".

Possibly related PRs

  • chore: Delay email and upgrade Resend #2152: This PR modifies the Resend class in internal/resend/src/client.tsx, specifically updating the same methods (sendTrialEnded, sendSubscriptionEnded, sendWelcomeEmail, sendPaymentIssue, and sendLeakedKeyEmail) that are also affected in the main PR, indicating a direct relationship in terms of changes made to the email sending logic.

Suggested reviewers

  • chronark

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2024

Thank you for following the naming conventions for pull request titles! 🙏

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)
internal/resend/src/client.tsx (3)

51-51: LGTM: Email domain updated as intended. Consider addressing the TODO comment.

The from email address has been correctly updated to use the new dot com domain. This change aligns with the PR objective.

However, there's a TODO comment above this method suggesting it might be deprecated and unused. Consider removing this method if it's no longer needed to keep the codebase clean.


Line range hint 16-16: Consider updating the replyTo email address.

For consistency with the changes made to the from email addresses, consider updating the replyTo email address to use the new dot com domain as well.

Suggested change:

-  private readonly replyTo = "support@unkey.dev";
+  private readonly replyTo = "support@unkey.com";

Line range hint 11-11: Consider renaming the Resend class for clarity.

The class name Resend might be confusing as it's not directly related to resending emails. Consider using a more descriptive name that reflects its purpose, such as EmailService or UnkeyEmailClient.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0d30308 and 79af809.

📒 Files selected for processing (1)
  • internal/resend/src/client.tsx (5 hunks)
🔇 Additional comments (4)
internal/resend/src/client.tsx (4)

27-27: LGTM: Email domain updated as intended.

The from email address has been correctly updated to use the new dot com domain. This change aligns with the PR objective and doesn't affect the method's functionality.


72-72: LGTM: Email domain updated as intended.

The from email address has been correctly updated to use the new dot com domain. This change aligns with the PR objective and doesn't affect the method's functionality.


96-96: LGTM: Email domain updated as intended.

The from email address has been correctly updated to use the new dot com domain. This change aligns with the PR objective and doesn't affect the method's functionality.


121-121: LGTM: Email domain updated as intended.

The from email address has been correctly updated to use the new dot com domain. This change aligns with the PR objective and doesn't affect the method's functionality.

@perkinsjr perkinsjr changed the title Chore: Update to dot com chore: Update to dot com Oct 2, 2024
@perkinsjr perkinsjr enabled auto-merge October 2, 2024 18:59
@perkinsjr perkinsjr disabled auto-merge October 2, 2024 21:06
@perkinsjr perkinsjr merged commit 5d70ab5 into main Oct 2, 2024
@perkinsjr perkinsjr deleted the update-email-address branch October 2, 2024 21:06
harshsbhat pushed a commit to harshsbhat/unkey that referenced this pull request Oct 3, 2024
* Update to dot com

We has dot com, we should use it.

* [autofix.ci] apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
mcstepp pushed a commit that referenced this pull request Oct 8, 2024
* Update to dot com

We has dot com, we should use it.

* [autofix.ci] apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
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.

1 participant