Repository navigation
fix(setup): allow anonymous UI installs and fork contributions - #171
Merged
Merged
Conversation
- 说明私有 UI 包权限、fork CI 与实际 setup 前提 - 区分实现项目命名和 Changeset 发布范围 - 记录公开 tarball 消费切换顺序，不改动有效 lockfile
- Ask for the needed feedback, next responder, and outstanding delivery work - Link cross-repository changes to their tracking issue
- Preserve current main changes before reviewing contribution delivery.
- Route the two existing UI versions to byte-identical public Release assets. - Remove npm authentication from workspace installation and dependency automation. - Preserve Module Federation semver and contributor handoffs.
github-project-automation
Bot
moved this from Review / acceptance
to Done
in InKCre Current Work
This was referenced Oct 26, 2026
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
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.
Intent
External contributors could clone this public repository but could not install its private UI dependencies. Route the existing UI 2.3.0 and 2.5.0 dependencies to byte-identical public Release assets with exact-version root overrides, regenerate the lockfile, and remove npm authentication from CI, preview, and release installation steps.
Keep package.json dependency semver unchanged for Module Federation. Preserve the original SHA-512 values and all unrelated package resolutions. Dependabot leaves UI upgrades to the coordinated mirror/override update; other updates remain automated. Include the contribution guide and PR handoff fields prepared in #152.
Primary scope:
setup. Release projects: none; no product behavior or version change.Tracking: InKCre/.github#39. Supersedes #152 after this delivery is verified. No stacked parent or child PR.
Evidence
e7fa9af3e38066418b40980e9b7d49f7375d7e1d: Actions syntax, admitted Core resolution, Workspace contract, Web E2E, and browser-extension E2E. The workspace run reports zero reused packages during the frozen install, downloading the dependency set from the public URLs without npm authentication. Both trusted-preview jobs were skipped as required for a fork.Next action
Merged after explicit maintainer approval. The main commit is
59436e548e4a8b859dacad45f93561a41123b000; Web Pages, Core SDK, and first-party Extension delivery workflows all passed. Current main uses public UI URLs and contains the guide and handoff changes from the superseded #152. The real fork checks passed within the fork credential boundary, and both trusted previews were skipped.Risk and rollback
Adopting another UI version requires its original public asset and matching override before changing semver. Publicly downloaded copies cannot be recalled. Revert this consumer change to restore the previous lockfile and private-package setup; this does not remove published assets. UI version upgrades, production delivery, and merging this consumer PR are separate from this change's preparation and verification.