Skip to content

Conversation

@mfranzke
Copy link
Collaborator

@mfranzke mfranzke commented Sep 4, 2025

Proposed changes

Run the test that has been developed within #4921 for our current code to verify it fails.

Types of changes

  • Bugfix (non-breaking change that fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improvements to existing components or architectural decisions)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Further comments

Run the test that has been developed within #4921 for our current code to verify it fails.
@mfranzke mfranzke self-assigned this Sep 4, 2025
@changeset-bot
Copy link

changeset-bot bot commented Sep 4, 2025

⚠️ No Changeset found

Latest commit: 1774f20

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.

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

@mfranzke mfranzke added the 🧪test Improvements/bugs for testing-framework label Sep 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2025

@mfranzke
Copy link
Collaborator Author

mfranzke commented Sep 4, 2025

this PR was only meant to be a test for the test case being developed for #4921 against the current codebase.

@mfranzke mfranzke deleted the test-run-test-through-our-pipeline-with-current-code branch September 4, 2025 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🏘components 🧪test Improvements/bugs for testing-framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants