Skip to content

Ref(Capacitor): Update getting started from new projects#113913

Merged
priscilawebdev merged 10 commits intogetsentry:masterfrom
lucas-zimerman:lz/update-cap-gs
May 6, 2026
Merged

Ref(Capacitor): Update getting started from new projects#113913
priscilawebdev merged 10 commits intogetsentry:masterfrom
lucas-zimerman:lz/update-cap-gs

Conversation

@lucas-zimerman
Copy link
Copy Markdown
Contributor

@lucas-zimerman lucas-zimerman commented Apr 24, 2026

This PR updates the getting started of capacitor with the following changes:

  • Update project setup for Angular.
  • Add missing platforms like Vue/Nuxt
  • Remove Session replay (it will be removed on the current major)
  • Add Log instructions.

Next Steps

Close getsentry/sentry-capacitor#1203

evanpurkhiser and others added 2 commits April 24, 2026 13:23
…etsentry#113806)

The queue gate in `commit_context.py` reads `sentry:github_pr_bot` /
`sentry:gitlab_pr_bot` with `default=False`, but the task body in
`tasks.py` re-read the same option with `default=True`. getsentry#103525 flipped
the default to off everywhere but missed this call site, so if the
option was cleared between enqueue and execution the task would run
against the old default-on behavior.

Since the queue gate is the only enqueue path
(`commit_context.py:458-461`, called from
`queue_pr_comment_task_if_needed`),
the `default=True` branch is effectively dead in the common case, but
the asymmetry is a latent bug if the option is deleted between enqueue
and task pickup. Aligning the defaults to `False` matches the intent of
getsentry#103525.

Co-authored-by: Claude <noreply@anthropic.com>
Comment thread src/sentry/integrations/source_code_management/tasks.py Outdated
@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Apr 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

Comment thread tests/sentry/integrations/gitlab/tasks/test_pr_comment.py Outdated
Comment thread tests/sentry/integrations/gitlab/tasks/test_pr_comment.py Outdated
Co-authored-by: LucasZF <lucas-zimerman1@hotmail.com>
Comment thread tests/sentry/integrations/gitlab/tasks/test_pr_comment.py Outdated
Comment thread tests/sentry/integrations/github/tasks/test_pr_comment.py Outdated
Comment thread tests/sentry/integrations/github/tasks/test_pr_comment.py Outdated
Co-authored-by: LucasZF <lucas-zimerman1@hotmail.com>
Comment thread tests/sentry/integrations/github/tasks/test_pr_comment.py Outdated
@lucas-zimerman
Copy link
Copy Markdown
Contributor Author

GH got confused with the changes so I had to remove line by line

@lucas-zimerman lucas-zimerman marked this pull request as ready for review April 24, 2026 15:01
@lucas-zimerman lucas-zimerman requested a review from a team as a code owner April 24, 2026 15:01
Copy link
Copy Markdown
Contributor

@antonis antonis left a comment

Choose a reason for hiding this comment

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

LGTM!

@bruno-garcia
Copy link
Copy Markdown
Member

approving to unblock but we shouldn't need approval from the value discovery team for these changes, feel free to add yourself to the codeowner for the relevant wizard files

@lucas-zimerman
Copy link
Copy Markdown
Contributor Author

Adding a note that I can't merge PRs here

@bruno-garcia does it mean @antonis and @alwx should also be code owners for the React Native wizard files?

Copy link
Copy Markdown
Member

I'd add team-mobile or something. I'm just saying there's no need to have the team working on onboarding sign off on all new project wizard changes. Have the domain experts (SDK engineers) be code owners in addition at least

@priscilawebdev priscilawebdev enabled auto-merge (squash) May 6, 2026 09:39
@priscilawebdev priscilawebdev added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label May 6, 2026
@priscilawebdev priscilawebdev merged commit 6d067ac into getsentry:master May 6, 2026
80 of 86 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Insights(Cap-V4) Update insight page

5 participants