chore: release package(s) #476
Conversation
WalkthroughA changeset file documenting the addition of the Changes
Possibly related PRs
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
🧰 Additional context used🪛 LanguageToolpackages/pkg/CHANGELOG.md[uncategorized] ~13-~13: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION) ⏰ Context from checks skipped due to timeout of 90000ms (2)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|
Deploy preview for prettier ready! ✅ Preview Built with commit af063fb. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #476 +/- ##
=======================================
Coverage 86.69% 86.69%
=======================================
Files 10 10
Lines 203 203
Branches 57 57
=======================================
Hits 176 176
Misses 26 26
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
prettier-plugin-autocorrect
prettier-plugin-pkg
prettier-plugin-sh
prettier-plugin-sql
prettier-plugin-toml
commit: |
size-limit report 📦
|
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to af063fb in 1 minute and 10 seconds. Click for details.
- Reviewed
53lines of code in3files - Skipped
0files when reviewing. - Skipped posting
4draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .changeset/silver-shirts-relax.md:1
- Draft comment:
Deletion of the changeset file appears expected for release automation. Confirm that this removal is intentional. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
2. packages/pkg/package.json:15
- Draft comment:
The top-level 'types' field (index.d.cts) differs from the export for ESM (lib/index.d.ts). Confirm this divergence is intentional. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
3. packages/pkg/CHANGELOG.md:13
- Draft comment:
Typo: Consider changing "npm's document" to "npm's documentation" for clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is a very minor wording suggestion in a changelog file. While "documentation" may be marginally more formal than "document", the difference is trivial. The current wording is perfectly understandable. Making this change would create unnecessary work for a negligible benefit. The suggested wording is technically more conventional. A changelog is a form of documentation that will be read by users. While slightly more conventional, the benefit is too small to justify asking for changes. The current wording is clear enough for a changelog entry. Delete this comment. The suggested change is too minor and stylistic to be worth making in a changelog file.
4. packages/pkg/CHANGELOG.md:14
- Draft comment:
Typo: Consider changing "compatible to" to "compatible with". - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While the suggestion is technically correct - "compatible with" is more proper English than "compatible to" - changelogs are primarily functional documentation rather than marketing copy. The meaning is perfectly clear either way. Making authors fix minor grammar in changelogs creates unnecessary back-and-forth. The change would make the text more grammatically correct. Poor grammar in documentation could reflect badly on the project. The slight grammar improvement isn't worth the overhead of another review cycle. The current text is perfectly understandable. Delete this comment as it suggests a minor grammatical change that doesn't meaningfully improve understanding.
Workflow ID: wflow_VQO5nM9vdW3saIxn
You can customize 
af063fb to
f8e2cdd
Compare
|
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 master, this PR will be updated.
Releases
prettier-plugin-pkg@0.21.1
Patch Changes
#475
8f1aef9Thanks @Shinigami92! - feat(pkg): add optionpackageSortOrderPresetThis option allows you to specify a preset for sorting packages in the
package.jsonfile.The available presets are:
npm,npm-plus:npm: sorts bynpm's documentnpm-plus: sorts bysort-package-jsonand therefore is compatible toprettier-plugin-packagejsonSummary by CodeRabbit