From 21cdbe234bfa9fd6be42e636a1532e4c70a9090e Mon Sep 17 00:00:00 2001 From: ENvironmentSet Date: Mon, 1 Jun 2026 22:30:50 +0900 Subject: [PATCH 1/2] fix(plugin-sentry): add publishConfig access public so release can publish (FEP-2358) @stackflow/plugin-sentry was the only package missing `publishConfig: { access: "public" }`. Without it, scoped packages default to `restricted` access and `changeset publish` fails with E402 Payment Required (the @stackflow org has no private plan), reddening every Release run that hits the publish path and blocking the subsequent git tag / GitHub Release steps. Co-Authored-By: Claude Opus 4.8 (1M context) --- .changeset/plugin-sentry-publish-access.md | 7 +++++++ extensions/plugin-sentry/package.json | 3 +++ 2 files changed, 10 insertions(+) create mode 100644 .changeset/plugin-sentry-publish-access.md diff --git a/.changeset/plugin-sentry-publish-access.md b/.changeset/plugin-sentry-publish-access.md new file mode 100644 index 000000000..2f7772c4b --- /dev/null +++ b/.changeset/plugin-sentry-publish-access.md @@ -0,0 +1,7 @@ +--- +"@stackflow/plugin-sentry": patch +--- + +Add `publishConfig: { access: "public" }` so the release workflow can publish the package. + +`@stackflow/plugin-sentry` was the only package missing this field. Without it, scoped packages default to `restricted` access and `changeset publish` fails with `E402 Payment Required` (the @stackflow org has no private plan). This was masked while `0.1.0` matched the repo version (publish was skipped as "already published") and surfaced once `0.1.1` triggered an actual publish. diff --git a/extensions/plugin-sentry/package.json b/extensions/plugin-sentry/package.json index 21277e555..b7bc50c81 100644 --- a/extensions/plugin-sentry/package.json +++ b/extensions/plugin-sentry/package.json @@ -41,5 +41,8 @@ "@stackflow/esbuild-config": "^1.0.3", "esbuild": "^0.23.0", "typescript": "^5.5.3" + }, + "publishConfig": { + "access": "public" } } From 4a1781cc07123f500b33cc70d80460460c523597 Mon Sep 17 00:00:00 2001 From: ENvironmentSet Date: Mon, 1 Jun 2026 22:43:28 +0900 Subject: [PATCH 2/2] chore(plugin-sentry): make the changeset empty (no version bump) publishConfig is a release-metadata-only change with no public API / runtime behavior change, so it should not bump the package version. Keep an empty changeset to satisfy the `changeset status` PR gate without producing a release. Co-Authored-By: Claude Opus 4.8 (1M context) --- .changeset/plugin-sentry-publish-access.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/.changeset/plugin-sentry-publish-access.md b/.changeset/plugin-sentry-publish-access.md index 2f7772c4b..fde438479 100644 --- a/.changeset/plugin-sentry-publish-access.md +++ b/.changeset/plugin-sentry-publish-access.md @@ -1,7 +1,4 @@ --- -"@stackflow/plugin-sentry": patch --- -Add `publishConfig: { access: "public" }` so the release workflow can publish the package. - -`@stackflow/plugin-sentry` was the only package missing this field. Without it, scoped packages default to `restricted` access and `changeset publish` fails with `E402 Payment Required` (the @stackflow org has no private plan). This was masked while `0.1.0` matched the repo version (publish was skipped as "already published") and surfaced once `0.1.1` triggered an actual publish. +`publishConfig: { access: "public" }` 추가는 공개 API/런타임 변경이 없는 릴리스 메타데이터 수정이므로 버전 bump 없이 처리합니다. (PR `changeset status` 게이트 통과용 empty changeset)