Skip to content

Release: Patch 8.6.13#31492

Closed
github-actions[bot] wants to merge 8 commits intolatest-releasefrom
version-patch-from-8.6.12
Closed

Release: Patch 8.6.13#31492
github-actions[bot] wants to merge 8 commits intolatest-releasefrom
version-patch-from-8.6.12

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented May 16, 2025

This is an automated pull request that bumps the version from 8.6.12 to 8.6.13.
Once this pull request is merged, it will trigger a new release of version 8.6.13.
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: Fix using dates in expect statements #28413
  • 🐛 Bug: Controls: Fix boxShadow on empty controls #27193
  • 📦 Dependencies: React Native Web: Update react-native-web #31324
  • 🐛 Bug: Test: Make sure that lit arrays are not cloned #31435
  • 🔧 Maintenance: CLI: Add skip onboarding, recommended/minimal config #30930
  • 🐛 Bug: React Native Web: Fix expo router by setting JSX to automatic #31484
  • 📝 Documentation: Docs: Replace outdated MDX VSCode setting with a new one #31116

🍒 Manual cherry picking needed!

The following pull requests could not be cherry-picked automatically because it resulted in merge conflicts.
For each pull request below, you need to either manually cherry pick it, or discard it by replacing the "patch:yes" label with "patch:no" on the PR and re-generate this PR.

  • #28413: git cherry-pick -m1 -x 1bdc69c1f3035e6fb832472e2bba7605e6e99163
  • #31435: git cherry-pick -m1 -x 6f91cee5640075188cbb05b1e4a1aab5f7804c64
  • #30930: git cherry-pick -m1 -x dde78a0a694a88d9cfe4f916de62f97141495226

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.6.13

Greptile Summary

This patch release (8.6.13) includes multiple bug fixes and improvements across CLI onboarding, controls styling, date handling, and React Native Web compatibility.

  • Added new CLI onboarding experience in code/lib/create-storybook/src/initiate.ts with options for recommended/minimal configurations
  • Fixed box shadow styling for empty controls in code/lib/blocks/src/components/ArgsTable/Empty.tsx
  • Updated React Native Web Vite preset in code/frameworks/react-native-web-vite/src/preset.ts to use automatic JSX runtime
  • Modified array handling in code/lib/test/src/index.ts to prevent lit array cloning issues
  • Added global settings system in code/core/src/cli/globalSettings.ts for persisting user preferences

ghengeveld and others added 8 commits May 14, 2025 11:44
…ate-param

Core: Fix using dates in expect statements
(cherry picked from commit 1bdc69c)
Test: Make sure that lit arrays are not cloned
(cherry picked from commit 6f91cee)
CLI: Add skip onboarding, recommended/minimal config
(cherry picked from commit dde78a0)
Controls: Fix boxShadow on empty controls
(cherry picked from commit ebd2976)
Docs: Replace outdated MDX VSCode setting with a new one
(cherry picked from commit 1137866)
Dependencies: Update `react-native-web`
(cherry picked from commit c92d13b)
React Native Web: Fix expo router by setting JSX to automatic

(cherry picked from commit 50b17fa)
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label May 16, 2025
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label May 16, 2025
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.

28 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines +48 to +51
/**
* A class for reading and writing settings from a JSON file. Supports nested settings with dot
* notation.
*/
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: Comment mentions dot notation support but implementation appears to be missing this functionality

settings = {
value: { version: 1 },
save: vi.fn(),
} as any as Settings;
Copy link
Contributor

Choose a reason for hiding this comment

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

style: Type assertion could be replaced with proper type definition

Comment on lines +141 to +150
it('uses specific prompt options for React Native projects', async () => {
prompts.inject(['recommended']);
const result = await promptInstallType({
settings,
projectType: ProjectType.REACT_NATIVE,
});

expect(result).toBe('recommended');
expect(prompts).not.toHaveBeenCalled();
expect(vi.mocked(telemetry).mock.calls[0][1]).toMatchInlineSnapshot(`
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: Test case doesn't match behavior - says it uses specific prompt options but expects prompts not to be called

Suggested change
it('uses specific prompt options for React Native projects', async () => {
prompts.inject(['recommended']);
const result = await promptInstallType({
settings,
projectType: ProjectType.REACT_NATIVE,
});
expect(result).toBe('recommended');
expect(prompts).not.toHaveBeenCalled();
expect(vi.mocked(telemetry).mock.calls[0][1]).toMatchInlineSnapshot(`
it('skips prompts for React Native projects', async () => {
prompts.inject(['recommended']);
const result = await promptInstallType({
settings,
projectType: ProjectType.REACT_NATIVE,
});
expect(result).toBe('recommended');
expect(prompts).not.toHaveBeenCalled();
expect(vi.mocked(telemetry).mock.calls[0][1]).toMatchInlineSnapshot(`

@shilman shilman closed this May 20, 2025
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.

6 participants