Conversation
added 7 commits
April 23, 2026 08:22
…PRs) Required status checks on main were blocking Release PRs from merging. Previous pattern: 'if:' skip of the whole job — GitHub never reports a status, required check waits forever. New pattern: job always runs, steps conditionally skip based on head ref. Release PRs merge cleanly. Also: - check-imports: REVERT warn-only; restore to fatal throw. Relative imports MUST have .js extensions for native-ESM-compatible output (per review). - setup-publish: stop gitignoring src/**/*.d.ts (hand-written type declarations like colors.d.ts are legit src files; only .js.map is strictly tsc output).
…nt-team option - 'linked build' now early-errors if package.json lacks 'linkedPackage: true'. linkedApp gets a pointer to 'linked build-app' instead; packages with no flag get a clear message. - setup-publish: new --grant-team <slug> option. Calls gh api to PUT team push-permission on the repo. Handy for core packages so maintainers (semantu-devs) get access without per-repo invites. - Team slug is variable, so community-package promotion flows can use a different team if desired (or omit entirely — community repos are maintainer-owned).
…h auth The prepack script 'yarn build && pinst --disable' ran during 'npm publish' and caused ENEEDAUTH — the publish couldn't authenticate against the registry. CI already runs the Build step explicitly, so prepack is redundant. Removed prepack/postpack/postinstall; bumped to 1.3.1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the
ENEEDAUTHfailure on PR #18's Release publish. Also includes additional improvements.Publish fix (primary)
prepack: yarn build && pinst --disable— was breaking npm's auth flowpostpack: pinst --enableandpostinstall: husky install— unnecessary for CI flowAdditional improvements
linked buildnow refuses to build non-linkedPackage packages (errors early, pointing linkedApp users tolinked build-app)linked setup-publish --grant-team <slug>new option (calls gh api to grant team push access; generic, no org-specific hardcoding)On merge: changesets opens a Release PR bumping to 1.3.1 with CHANGELOG. Merging that publishes.