Skip to content
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

Release: Prerelease 8.5.0-alpha.11 #29700

Open
wants to merge 22 commits into
base: next-release
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 25, 2024

This is an automated pull request that bumps the version from 8.5.0-alpha.10 to 8.5.0-alpha.11.
Once this pull request is merged, it will trigger a new release of version 8.5.0-alpha.11.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

  • Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
  • Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

  1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
  2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
  3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
    • Areas include: React, Vue, Core, Docs, Controls, etc.
    • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
    • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

  • 🐛 Bug: Core + Addon Test: Refactor test API and fix total test count #29656
  • 🏗️ Build: Revert "Build: Add workaround resolution for Angular sandboxes" #29695

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:


Generated changelog

8.5.0-alpha.11

  • Core + Addon Test: Refactor test API and fix total test count - #29656, thanks @ghengeveld!

Greptile Summary

Here's my summary of the key changes in this pull request:

Refactored test API and improved test execution in Storybook, focusing on simplifying the interface and improving accuracy.

  • Consolidated test execution into single TESTING_MODULE_RUN_REQUEST event, removing separate "run all" event
  • Simplified test request payload to use indexUrl and optional storyIds parameters
  • Added server-side story index fetching to ensure tests only run for existing stories
  • Improved test progress accuracy by using static story count from index
  • Removed Angular sandbox workarounds that are no longer needed

The changes appear well-tested and maintain backward compatibility while significantly improving the testing infrastructure. The version bump from 8.5.0-alpha.10 to 8.5.0-alpha.11 is appropriate for these changes.

ghengeveld and others added 22 commits November 18, 2024 16:40
…use the story index to count the total number of tests and only run tests known by Storybook
…lar-sandboxes-ci

Revert "Build: Add workaround resolution for Angular sandboxes"
Core + Addon Test: Refactor test API and fix total test count
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label Nov 25, 2024
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

25 file(s) reviewed, 4 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines +82 to +85
const index = (await Promise.race([
fetch(indexUrl).then((res) => res.json()),
new Promise((_, reject) => setTimeout(reject, 3000, new Error('Request took too long'))),
])) as StoryIndex;
Copy link
Contributor

Choose a reason for hiding this comment

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

style: Consider increasing timeout from 3000ms for slower networks/larger story indexes

Comment on lines +102 to +104
__VITEST_INCLUDE_TAGS__: finalOptions.tags.include.join(','),
__VITEST_EXCLUDE_TAGS__: finalOptions.tags.exclude.join(','),
__VITEST_SKIP_TAGS__: finalOptions.tags.skip.join(','),
Copy link
Contributor

Choose a reason for hiding this comment

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

style: Environment variables should be prefixed with STORYBOOK_ to avoid potential conflicts with other tools

Comment on lines 84 to 86
'@testing-library/dom': '^9.3.4',
'@testing-library/jest-dom': '^6.5.0',
'@testing-library/user-event': '^14.5.2',
Copy link
Contributor

Choose a reason for hiding this comment

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

style: Testing library dependencies use caret ranges while other deps use exact versions - should be consistent

Comment on lines 138 to 139
await runTestsButton.click();

await expect(runTestsButton).toBeDisabled();
await expect(watchModeButton).toBeDisabled();
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: The removed expectation for disabled run button suggests tests can now be triggered while another test is running. Verify this is intentional and won't cause race conditions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release For PRs that trigger new releases. Automated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants