chore: add changesets foundation config#381
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdds a new Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.changeset/config.json (1)
6-6: When release automation is implemented, align theaccesssetting with your publishing strategy.The changeset configuration is currently a placeholder for future release automation. When you implement publishing for
stackchan-web(an unscoped package), update"access"to"public"rather than"restricted", as"restricted"is intended for scoped packages only.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.changeset/config.json at line 6, The changeset config currently sets "access" to "restricted", which is only appropriate for scoped packages; when you implement release automation and intend to publish the unscoped package "stackchan-web", change the "access" value in .changeset/config.json from "restricted" to "public" so the publishing strategy matches the package scope and avoids access-related publish failures.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/config.json:
- Line 2: Update the JSON schema URL value for the "$schema" key to reference
the latest Changesets config schema version: replace
"https://unpkg.com/@changesets/[email protected]/schema.json" with
"https://unpkg.com/@changesets/[email protected]/schema.json" so the config uses the
3.1.3 schema; modify the string value associated with the "$schema" property in
the file accordingly.
---
Nitpick comments:
In @.changeset/config.json:
- Line 6: The changeset config currently sets "access" to "restricted", which is
only appropriate for scoped packages; when you implement release automation and
intend to publish the unscoped package "stackchan-web", change the "access"
value in .changeset/config.json from "restricted" to "public" so the publishing
strategy matches the package scope and avoids access-related publish failures.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a44c221e-7266-4ea6-91c4-1ae8776b3806
📒 Files selected for processing (2)
.changeset/README.md.changeset/config.json
1 participant
Adds repository-level Changesets configuration as non-invasive release-note scaffolding anchored to dev/v1.0.
Summary by CodeRabbit