Skip to content

fix: bring back webcomponnets#34504

Merged
fmontes merged 2 commits intomainfrom
fix-broken-webcomponents
Feb 4, 2026
Merged

fix: bring back webcomponnets#34504
fmontes merged 2 commits intomainfrom
fix-broken-webcomponents

Conversation

@fmontes
Copy link
Copy Markdown
Member

@fmontes fmontes commented Feb 4, 2026

Proposed Changes

  • change 1
  • change 2

Checklist

  • Tests
  • Translations
  • Security Implications Contemplated (add notes if applicable)

Additional Info

** any additional useful context or info **

Screenshots

Original Updated
** original screenshot ** ** updated screenshot **

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 4, 2026

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes #123 or Fixes: #123

  • This PR closes #123 or Closes: #123

  • This PR resolves #123 or Resolves: #123

  • Other supported keywords: fix, fixed, close, closed, resolve, resolved
    Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

@oidacra oidacra linked an issue Feb 4, 2026 that may be closed by this pull request
5 tasks
@erickgonzalez erickgonzalez added this pull request to the merge queue Feb 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Feb 4, 2026
@nollymar nollymar added this pull request to the merge queue Feb 4, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Feb 4, 2026
@fmontes fmontes added this pull request to the merge queue Feb 4, 2026
Merged via the queue into main with commit 046609d Feb 4, 2026
18 checks passed
@fmontes fmontes deleted the fix-broken-webcomponents branch February 4, 2026 23:18
dsolistorres pushed a commit that referenced this pull request Feb 20, 2026
### Proposed Changes
* change 1
* change 2

### Checklist
- [ ] Tests
- [ ] Translations
- [ ] Security Implications Contemplated (add notes if applicable)

### Additional Info
** any additional useful context or info **

### Screenshots
Original             |  Updated
:-------------------------:|:-------------------------:
** original screenshot **  |  ** updated screenshot **
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[TASK] Rollback PR #33941 - Re-enable Web Components in Angular Project

3 participants