Skip to content

fix(changesets): change to public access #222

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.

Sign up for GitHub

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

Merged
cabljac merged 1 commit into from
Aug 27, 2025
Merged

fix(changesets): change to public access #222

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .changeset/config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"commit": false,
"fixed": [],
"linked": [],
"access": "restricted",
"access": "public",
Copy link

@gemini-code-assist gemini-code-assist bot Aug 27, 2025

Choose a reason for hiding this comment

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

critical

Setting the default access to public creates a significant risk of accidentally publishing private or proprietary packages. Any new package added to this repository will be publicly available by default upon publishing, unless its access level is explicitly overridden in its package.json. If this repository is intended to house any private packages, this default should remain restricted to prevent accidental data leaks.

"baseBranch": "main",
"updateInternalDependencies": "patch",
"ignore": ["example-*"]
Expand Down