Skip to content

Exclude angular-pacer and pacer-devtools from fork publishing - #8

Closed
dogmar wants to merge 1 commit into
mainfrom
fix/exclude-unpublished-packages
Closed

dogmar wants to merge 1 commit into
mainfrom
fix/exclude-unpublished-packages

Conversation

@dogmar

@dogmar dogmar commented Mar 30, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Exclude angular-pacer and pacer-devtools from fork publishing — the fork doesn't modify these packages, so publishing them under @klinking is unnecessary
  • Skip these packages in the CI version-detection step so they don't trigger publish attempts
  • Fixes ENEEDAUTH failures in publish-fork run #23763760225: these packages were never published to @klinking so had no OIDC trust relationship for --provenance

Test plan

  • Merge and verify the next publish-fork run succeeds
  • Confirm angular-pacer and pacer-devtools no longer appear in "Packages to publish" logs

https://claude.ai/code/session_01SS17WVK4qWuwuiaeyD4fHb

…ishing

These packages have no fork-specific modifications:
- angular-pacer: fork doesn't update the Angular adapter
- pacer-devtools: upstream devtools works as-is with the maxWait feature

Excluding them fixes ENEEDAUTH failures (they were never published to
@Klinking so had no OIDC trust relationship) and avoids unnecessary
publishes.

https://claude.ai/code/session_01SS17WVK4qWuwuiaeyD4fHb
@dogmar dogmar closed this Mar 30, 2026
@dogmar
dogmar deleted the fix/exclude-unpublished-packages branch March 30, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant