Repository navigation
chore(nameservice): integrate open pull requests into develop - #146
Merged
Merged
Conversation
# Conflicts: # pnpm-lock.yaml
This was referenced Oct 5, 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
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.
Integration of open pull requests into develop
Automated integration run (base develop
2147c60277e0b6cd04fa8dacb91d898d7a753671).Direct push to
developis rejected by branch protection (GH006: Changes must be made through a pull request), so the exact integration chain — baseline2147c60+ one merge commit per integrated PR — is delivered through this PR. After this PR merges with Create a merge commit (or its branch simply fast-forwards), every integrated PR head becomes an ancestor ofdevelopand GitHub will attribute the corresponding PRs as merged.Merged (one merge commit per PR, ascending)
9e4fca0abea62e9063d0349aacb0db7a93818f2f1ed0d0bb9c68121e59798c24eca0e23e49059adc8a23ae712ecccce6937ce2d57c90f06cfd1dcf2cb85a2f5f2e27abc1863543baf5e3f45de4f0727fConflict resolutions (union of intents)
pnpm install --lockfile-only), keeping npm-check-updates@23 (from chore(deps): update dependency npm-check-updates to v23 - autoclosed #141) inside the maintenance-regenerated lock of chore(deps): lock file maintenance #145. Verified: ncu@23 present, ncu@12 tree fully pruned, no conflict markers,pnpm install/build/lint/test:unitgreen after the merge.Blocked (excluded from this integration, left open for maintainers)
latest-version@9is ESM-only; jest-runtime (Node 24.10, no--experimental-vm-modulesin repo config) throwsERR_REQUIRE_ESMinpnpm test:unit. Repo CI on the PR head fails the same UNIT step (run 37210264660). Union repair impossible: pinning 8.x discards the PR intent.typescript@7.0.2(native compiler) exposes no JS compiler API:pnpm build(tsc),pnpm lint(typescript-eslint) andpnpm test:unit(ts-jest) all exit non-zero. Repo CI on the PR head fails every workflow (run 37241525510). Union repair impossible without net-new tooling outside both sides.Gates
After every individual merge:
pnpm install→pnpm build→pnpm lint→pnpm test:unit, all exit 0 (crypto 7 tests, api 4 tests, transactions 13 tests). Full suite re-verified at this branch head; no conflict markers in tracked files.