fix(plugin-sentry): add publishConfig access public so release can publish (FEP-2358)

[ENvironmentSet]

배경

stackflow는 npm OIDC trusted publishing으로 배포한다(release.yml). @stackflow/plugin-sentry는 신규 패키지라 첫 배포(0.1.0)를 로컬에서 수동 부트스트랩한 뒤 이후 버전부터 CI가 인계받는 흐름인데, 이 패키지에만 publishConfig: { access: "public" }가 없다(이력상 한 번도 없음).

그래서 scoped 패키지 기본값인 restricted로 게시가 나가고, @stackflow org에 private 플랜이 없어 changeset publish가 E402 Payment Required로 실패한다. 0.1.0이 레포 버전과 같던 동안은 CI가 "이미 게시됨"으로 skip해 가려져 있었고, #709에서 0.1.1로 bump되며 CI가 실제 게시를 시도하는 순간 드러났다. 부수 효과로 publish 스텝이 sentry에서 비정상 종료 → changesets action의 후속 단계(git 태그 + GitHub Release 생성)가 미실행됐다.

변경

• extensions/plugin-sentry/package.json에 다른 모든 패키지와 동일하게 "publishConfig": { "access": "public" } 추가
• empty changeset 추가 — publishConfig는 공개 API/런타임 변경이 없는 릴리스 메타데이터 수정이라 버전 bump 없이 처리. PR의 changeset status 게이트만 통과시킨다.

머지 후 동작 (의도)

changesets/action@v1은 "changeset이 존재하지만 전부 empty"인 경우 publish 경로보다 먼저 All changesets are empty; not creating PR로 early-return한다. 따라서:

1. 이 PR 머지 → main에 publishConfig 반영 + empty changeset 존재 → 다음 Release run은 publish를 시도하지 않고 early-return → 지금까지 매 run 터지던 E402 red가 멈춘다.
2. 단, empty changeset만 단독으로 남아있는 동안은 Release 자동화가 정지 상태이고 plugin-sentry@0.1.1은 자동 게시되지 않는다.
3. 실제 0.1.1 게시는 empty changeset이 비워질 때 일어난다 — 후속에서 제거하거나, 다음 비어있지 않은 changeset의 Version PR가 함께 소비한 뒤 main에 changeset이 없어지면 publish 경로가 돌아 0.1.1(현재 버전 그대로)을 public으로 게시한다.

확인 사항

• publishConfig: {access: "public"} 추가 (+ empty changeset)
• 머지 후 Release run에서 E402 red 해소(green) 확인
• plugin-sentry@0.1.1 게시 트리거(empty changeset 정리 시점) 확인

Resolves FEP-2358

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: 4a1781c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Enabled public publishing for the Sentry plugin package to allow public distribution.
  • Added a release metadata entry recording this publish-config update (no runtime or API changes).

Walkthrough

Adds publishConfig: { access: "public" } to extensions/plugin-sentry/package.json and creates a .changeset entry documenting this metadata-only release change.

Changes

Plugin Sentry Publish Access

Layer / File(s)	Summary
Publish access + changeset extensions/plugin-sentry/package.json, .changeset/plugin-sentry-publish-access.md	Adds publishConfig: { access: "public" } to the package manifest and adds a changeset entry describing the release-metadata-only update.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding publishConfig with access public to fix the publication issue for plugin-sentry.
Description check	✅ Passed	The description is detailed and directly related to the changeset, explaining the background, changes, and expected behavior after merge.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/fep-2358

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

• @stackflow/demo

  yarn add https://pkg.pr.new/@stackflow/plugin-sentry@715.tgz
  

commit: 4a1781c

[cloudflare-workers-and-pages]

Deploying stackflow-demo with    Cloudflare Pages

Latest commit:	4a1781c
Status:	✅  Deploy successful!
Preview URL:	https://476802d8.stackflow-demo.pages.dev
Branch Preview URL:	https://feature-fep-2358.stackflow-demo.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	stackflow-docs	4a1781c	Commit Preview URL	Jun 01 2026, 01:47 PM