Migrate library publishing to GitHub Packages [WPB-26998]#21813
Closed
screendriver wants to merge 1 commit into
Closed
Migrate library publishing to GitHub Packages [WPB-26998]#21813screendriver wants to merge 1 commit into
screendriver wants to merge 1 commit into
Conversation
screendriver
requested review from
arjita-mitra,
e-maad,
ikotarac,
otto-the-bot,
thisisamir98 and
zskhan
as code owners
July 13, 2026 06:59
Publish the repository libraries through the GitHub Packages npm registry instead of npmjs.com. Use the repository GITHUB_TOKEN for authentication, keep dependency installation on npmjs.com, and configure the registry explicitly for each published package. Update the release workflow and publishing documentation to reflect the new registry, permissions, authentication, and consumer setup. Document the remaining cross-repository dependency on @wireapp/protocol-messaging.
screendriver
force-pushed
the
github-packages
branch
from
July 13, 2026 07:10
09389bf to
239f063
Compare
|
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.
This pull request moves the web-app library publishing process from npmjs.com to the GitHub Packages npm registry.
The existing Nx Release flow remains unchanged: the first workflow creates a versioning pull request, and the second workflow publishes the packages after that pull request is merged.
Publishing now uses the repository’s
GITHUB_TOKENthroughNODE_AUTH_TOKENand requirespackages: write. The npmjs.com trusted publishing and provenance configuration are no longer needed.Package publishing is configured explicitly through each publishable package’s
publishConfig. The root registry configuration remains pointed at npmjs.com so that regular dependencies continue to install normally. GitHub Packages is configured only for the publishing step to avoid redirecting all@wireapp/*dependencies during installation.The runtime dependency graph of
@wireapp/api-clientwas also reviewed. Repository-local packages that are required by consumers are included in the release setup where necessary.@wireapp/protocol-messagingis maintained in a separate repository. It must also be available through GitHub Packages before consumers can install@wireapp/api-clientexclusively from the GitHub registry.The publishing documentation now covers the GitHub Packages workflow, authentication for local development and GitHub Actions, package access configuration, manual publishing, and the existing squash-merge tag-retargeting behaviour.
Follow-up
The
@wireapp/protocol-messagingpackage must be migrated in thewireapp/generic-message-protorepository before the complete@wireappdependency chain can be consumed through GitHub Packages.