NEARBuilders / NEARBuilders/everything-dev

orpc-v2: sync citynode.app main with everything-dev (pull the 5 commits)

Open
#249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ready-for-agent
Dominant language
TypeScript
Stars
5
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Description

Ticket ID: M0

Parent

#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)

What to build

Bring citynode.app main up to date with everything-dev main (upstream is 5 commits ahead: relayer fixes, null overrides, send, lint, version packages) so the fork becomes a strict superset of upstream and the M1 merge is a clean fast-forward.

Resolve conflicts where both sides touched the same files — the auth plugin's relayer configuration is the expected hotspot. Preserve both intents: upstream's relayer/null-override fixes and the fork's auth-plugin work.

Acceptance criteria

  • citynode.app main contains every everything-dev main commit (zero behind, still ahead)
  • Conflicts resolved preserving upstream's relayer/override fixes and the fork's auth work
  • bun run test, bun typecheck, bun lint green on the merged main
  • Fork runtime identity untouched (bos.config.json account/gateway/deploy URLs unchanged)

Blocked by

None (can start immediately).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare citynode.app main with everything-dev main and review the five upstream commits before merging. Resolve the auth-plugin relayer conflict while retaining both sides' changes, then run bun run test, bun typecheck, and bun lint; done means the branch is zero commits behind, still ahead, and bos.config.json identity values are unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
bun, git, typescript
Domain
devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.