Skip to content

Update docs with steps to upgrade the version in Dotcom #83

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 10, 2025

Conversation

jibrang
Copy link
Contributor

@jibrang jibrang commented Apr 10, 2025

We are updating the README to include a section on upgrading the browser-support package in Dotcom. This section includes a set of steps to ensure a safe upgrade process while maintaining uninterrupted browser error reporting to Sentry.

@Copilot Copilot bot review requested due to automatic review settings April 10, 2025 20:06
@jibrang jibrang requested a review from a team as a code owner April 10, 2025 20:06
@jibrang jibrang requested a review from arelia April 10, 2025 20:06
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the README to include clear instructions for upgrading the browser-support package in Dotcom while ensuring continuous error reporting to Sentry.

  • Added a new section outlining steps for lab testing and production deployment to validate error reporting.
  • Provided environment-specific browser error testing instructions with detailed links for Sentry and monitor checks.

@jibrang jibrang force-pushed the jibrang/update-docs branch from e032493 to de864ca Compare April 10, 2025 20:07
Add example.

Co-authored-by: Arelia Jones <[email protected]>
@jibrang jibrang requested a review from arelia April 10, 2025 20:20
@jibrang jibrang merged commit b327773 into main Apr 10, 2025
5 checks passed
@jibrang jibrang deleted the jibrang/update-docs branch April 10, 2025 20:22
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