You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
synckit@0.11.3
Patch Changes
#228cc7c724 Thanks @JounQin! - fix: legacy top level types entry should prefer .d.cts
Summary by CodeRabbit
Bug Fixes
Resolved an issue to enhance internal consistency.
Documentation
Updated release notes to include details for the latest patch release.
Chores
Bumped the package version to 0.11.3 to deliver the improvements.
The pull request removes a changeset file that documented a patch for the legacy top-level types entry, recommending the .d.cts format. It also updates the CHANGELOG.md by adding a new section for version 0.11.3, which documents the patch with a commit hash and pull request reference. Additionally, the package version in package.json has been updated from 0.11.2 to 0.11.3. No changes were made to the declarations of exported or public entities.
Changes
Files
Change Summary
.changeset/funny-bobcats-fly.md
Deleted file that documented a patch fix for the legacy top-level types entry, recommending preference for the .d.cts format.
CHANGELOG.md, package.json
Updated release information to version 0.11.3: Added a new changelog entry detailing the patch (with commit and PR reference) and updated the package version accordingly.
Possibly related PRs
chore: release synckit #221: Addresses similar issues with the legacy top-level types entry in the context of version updates.
chore: release synckit #227: Fixes related handling of .cts files, complementing the changes for the legacy top-level types entry.
chore: bump all (dev) deps #228: Directly handles the legacy top-level types entry fix by specifying the preference for the .d.cts format.
Poem
I'm a bunny with a cheerful hop,
Code updates make my heart go pop,
Bugs and clutter, I watch them drop,
Version bump sounds—let the changes rock,
Hopping in codefields with a joyful bop!
📜 Recent review details
Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between cc7c724 and cf901e3.
📒 Files selected for processing (3)
.changeset/funny-bobcats-fly.md (0 hunks)
CHANGELOG.md (1 hunks)
package.json (1 hunks)
💤 Files with no reviewable changes (1)
.changeset/funny-bobcats-fly.md
⏰ Context from checks skipped due to timeout of 90000ms (11)
GitHub Check: Codacy Static Code Analysis
GitHub Check: Lint and Test with Node.js 22 on windows-latest
GitHub Check: Lint and Test with Node.js 23 on windows-latest
GitHub Check: Lint and Test with Node.js 23 on macos-latest
GitHub Check: Lint and Test with Node.js 20 on windows-latest
GitHub Check: Lint and Test with Node.js 22 on ubuntu-latest
GitHub Check: Lint and Test with Node.js 18 on macos-latest
GitHub Check: Lint and Test with Node.js 22 on macos-latest
GitHub Check: Lint and Test with Node.js 23 on ubuntu-latest
GitHub Check: Lint and Test with Node.js 18 on windows-latest
GitHub Check: Lint and Test with Node.js 18.18 on windows-latest
🔇 Additional comments (2)
package.json (1)
3-3: Version Bump to 0.11.3 Confirmed
The version field has been updated from "0.11.2" to "0.11.3", which correctly reflects the intended release. Please verify that all accompanying release changes are in sync with this update.
CHANGELOG.md (1)
3-8: Changelog Update for Release 0.11.3
The new changelog section clearly documents the patch change for the legacy top-level types entry, including the relevant pull request reference and commit hash. The formatting and content conform to the project's changelog style. Ensure this entry is consistent with the overall release notes and that no additional changes are omitted.
Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.
Generate unit testing code for this file.
Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
@coderabbitai generate unit testing code for this file.
@coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
@coderabbitai read src/utils.ts and generate unit testing code.
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
@coderabbitai help me debug CodeRabbit configuration file.
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (Invoked using PR comments)
@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
synckit@0.11.3
Patch Changes
cc7c724Thanks @JounQin! - fix: legacy top leveltypesentry should prefer.d.ctsSummary by CodeRabbit