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.6.0-alpha.4 #30439

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

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 1, 2025

This is an automated pull request that bumps the version from 8.6.0-alpha.3 to 8.6.0-alpha.4.
Once this pull request is merged, it will trigger a new release of version 8.6.0-alpha.4.
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: Vite: Fix add component UI invalidation #30438 (will also be patched)
  • 📝 Documentation: RNW-Vite: Fix typos #30437 (will also be patched)
  • 📝 Documentation: Docs: Add Preact-vite framework docs #30271 (will also be patched)
  • 📝 Documentation: Docs: Update Next.js Tailwind example link #30412 (will also be patched)
  • 🏗️ Build: Build: Upgrade typescript #30354

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.0-alpha.4

Greptile Summary

Based on the provided information, I'll create a concise summary of the PR that bumps the version from 8.6.0-alpha.3 to 8.6.0-alpha.4:

This release includes a Vite bug fix, documentation improvements, and a TypeScript upgrade to enable module mocking functionality.

  • Fixed Vite's add component UI invalidation in code/builders/builder-vite/src/plugins/code-generator-plugin.ts to properly handle HMR for new stories
  • Added Preact-vite framework documentation and fixed typos in React Native Web Vite docs
  • Updated Next.js Tailwind example link to reflect current repository structure
  • Upgraded TypeScript from 5.3.2 to 5.7.3 across codebase to enable module mocking via package.json imports field
  • Performance impact: 22.5% slowdown in devAutodocsVisible metric after TypeScript upgrade

The changes appear appropriate for a prerelease version bump, with proper testing and documentation updates included.

shilman and others added 30 commits January 16, 2025 11:27
Docs: Update Next.js Tailwind example link
…-component-ui

Vite: Fix add component UI invalidation
@github-actions github-actions bot requested a review from kylegach as a code owner February 1, 2025 16:56
@github-actions github-actions bot added the release For PRs that trigger new releases. Automated label Feb 1, 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.

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

@@ -56,14 +56,14 @@
"@storybook/vue3": "workspace:*",
"find-package-json": "^1.2.0",
"magic-string": "^0.30.0",
"typescript": "^5.0.0",
"typescript": "^5.7.3",
Copy link
Contributor

Choose a reason for hiding this comment

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

style: typescript dependency is duplicated in both dependencies and devDependencies - consider removing from one location

Suggested change
"typescript": "^5.7.3",


#### `builder`

Type: `Record<string, any>`
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 adding more specific type information beyond Record<string, any>

@@ -42,7 +42,7 @@ const isVersionPublished = async ({
`Unexpected status code when checking the current version on npm: ${response.status}`
);
}
const data = await response.json();
const data: any = await response.json();
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 defining a TypeScript interface for the npm registry response data structure instead of using any

@@ -13,7 +13,7 @@ export const githubClient = (apiKey: string) => {
}),
});

const result = await res.json();
const result: any = await res.json();
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 defining a proper interface for the GitHub API response instead of using any to maintain type safety

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