Skip to main content

Package preview failures

Fix missing pkg.pr.new links without exposing fork code to credentials.

Confirm that pkg.pr.new is enabled for the repository and that the workflow ran for the exact pull request SHA.

A package is missing

Compare the repository's public package inventory with the preview command and manifest. Add every independent package. Build local package dependencies in the correct order before publication.

A fork preview does not run

This is expected under the Lupinum policy. Automatic package previews run only for branches inside lupinum-dev. Do not add privileged pull_request_target execution for arbitrary fork code.

An external contributor can provide verification evidence, or a maintainer can review the code and reproduce the branch within the organization.

The preview URL does not install

Inspect the preview job output and retained manifest. Confirm the package name, commit address, hash, and build output. Test the URL in a clean temporary consumer. Do not replace the preview with a local npm publication.