Skip to content

chore: add library version input field in bug report template #5565

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rubencarvalho
Copy link
Contributor

@rubencarvalho rubencarvalho commented Jun 25, 2025

Description

Added a new field to the GitHub bug report template prompting users to include the version of @spectrum-web-components they’re using when filing issues.

Motivation and context

While triaging recent bugs, I noticed that many reports were missing the library version. This information is often crucial for reproducing and resolving issues, especially when version-specific regressions or changes are involved

Author's checklist

  • I have read the CONTRIBUTING and PULL_REQUESTS documents.
  • I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
  • I have added automated tests to cover my changes.
  • I have included a well-written changeset if my change needs to be published.
  • I have included updated documentation if my change required it.

Reviewer's checklist

  • Includes a Github Issue with appropriate flag or Jira ticket number without a link
  • Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
  • Automated tests cover all use cases and follow best practices for writing
  • Validated on all supported browsers
  • All VRTs are approved before the author can update Golden Hash

Copy link

changeset-bot bot commented Jun 25, 2025

⚠️ No Changeset found

Latest commit: dbb48fe

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

Copy link

github-actions bot commented Jun 25, 2025

📚 Branch Preview

🔍 Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

Deployed to Azure Blob Storage: pr-5565

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

Copy link

Tachometer results

Currently, no packages are changed by this PR...

Rajdeepc
Rajdeepc previously approved these changes Jun 25, 2025
@Rajdeepc Rajdeepc dismissed their stale review June 25, 2025 14:26

Still in draft

@rubencarvalho rubencarvalho force-pushed the ruben/library-version-bug-report branch from 52d34cd to dbb48fe Compare June 26, 2025 08:50
@rubencarvalho rubencarvalho marked this pull request as ready for review June 26, 2025 08:50
@rubencarvalho rubencarvalho requested a review from a team as a code owner June 26, 2025 08:50
@rubencarvalho rubencarvalho requested a review from Rajdeepc June 26, 2025 08:50
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