Skip to content

Adopt section-pull-requests 0.4.0, and fix what blocked a fresh clone - #6

Open
AndreaSucreG wants to merge 1 commit into
mainfrom
feat/pr-section-0.4.0
Open

Adopt section-pull-requests 0.4.0, and fix what blocked a fresh clone#6
AndreaSucreG wants to merge 1 commit into
mainfrom
feat/pr-section-0.4.0

Conversation

@AndreaSucreG

@AndreaSucreG AndreaSucreG commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

Why

pnpm install on a fresh clone fails today: @asucregonzalez/ui is pinned ^0.3.0 but npm only had 0.2.0 published, so the template dies with ERR_PNPM_NO_MATCHING_VERSION. That version is now on npm.

Repinned to the three versions published today:

Package Was Now
section-pull-requests ^0.3.0 ^0.4.0
section-tasks ^0.2.0 ^0.3.0
ui ^0.2.0 ^0.3.0

What 0.4.0 brings

Stacked-PR chains, Jira stream attribution, scheduled checkpoint posting, and an author filter on the "mine" views. Two things it needs from the host app:

Jira's three env vars were declared nowhere. Now in .env.example, documented as opt-in — without them attribution degrades to "unattributed" rather than failing.

defaultOrganizations. The GitHub org used to be hardcoded inside the published package, which meant an install queried someone else's org and returned their PRs, or none — a failure that looks like success. The package now ships empty and the host names its own, read from VITE_GITHUB_ORGS. One variable for both server and client, so the org the settings UI suggests cannot drift from the org the server actually queries. Leaving it unset is safe: a fetch reports "no organizations configured" instead of rendering an empty list that reads as a quiet queue.

Two guide bugs

  • The Setup card told users to run make claude. No such target exists — it's make run, which the README already said correctly.
  • The drift check meant to catch an undocumented section was itself drifting. Its card claimed the guide group id while the check reads the flattened leaf list, so the card never rendered and setup/how-to/faq were reported undocumented on every load. A card can claim several ids now.

Also corrects the overview table (it omitted the Guide tab and the Claude sessions panel, and still described Day as an empty page) and the skill count.

Verification

  • pnpm install resolves all ten @asucregonzalez/* pins
  • tsc --noEmit && vite build passes

Claims in the docs were checked against this repo rather than copied from upstream — the Day row drops the "Run morning sync" button and refreshEnabled stays false, since this app mounts no /api/refresh route.

⚠️ Note: pnpm 11 gates packages published within ~24h. On a clone today it will auto-write minimumReleaseAgeExclude entries into pnpm-workspace.yaml on first install and proceed — deliberately not committed here, since it names three exact versions and goes stale.

🤖 Generated with Claude Code


Note

Low Risk
Mostly dependency bumps, env wiring, and documentation; PR routing behavior changes are configuration-driven with safe fallbacks when vars are unset.

Overview
Upgrades section-pull-requests, section-tasks, and ui so a fresh pnpm install resolves (the UI pin had been ahead of what was on npm). That unlocks PR section 0.4.0 behavior in the host app.

GitHub orgs are no longer implied by the package: VITE_GITHUB_ORGS is documented in .env.example and parsed in both src/App.tsx (defaultOrganizations for the UI) and server/index.ts (same list passed into registerPullRequestsRoutes), so suggested orgs and API queries stay aligned; unset orgs surface an explicit message instead of a silent empty queue.

Optional Jira env vars (JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN) are added to .env.example for stream attribution without breaking the PR list when omitted.

Docs and Guide fixes: README reflects Today / Archives / Guide navigation and current tabs; Guide Setup card uses make run instead of make claude; Guide cards can claim multiple section ids, and the Guide card now maps setup, how-to, and faq so the “undocumented sections” check stops false-alarming.

Reviewed by Cursor Bugbot for commit 075c2d1. Bugbot is set up for automated code reviews on this repo. Configure here.

The template pinned `@asucregonzalez/ui` at `^0.3.0` while npm had only 0.2.0
published, so `pnpm install` failed with ERR_PNPM_NO_MATCHING_VERSION. That
version is now published; repinned alongside section-pull-requests 0.4.0 and
section-tasks 0.3.0.

0.4.0 brings stacked-PR chains, Jira stream attribution, scheduled checkpoint
posting and an author filter. Two things it needs from the host:

- Jira's three env vars, which were declared nowhere. Documented in .env.example
  as opt-in — attribution degrades to "unattributed" rather than failing.
- `defaultOrganizations`. The GitHub org used to be hardcoded in the package, so
  an install queried someone else's org and returned their PRs, or none. It now
  ships empty and the host names its own, from VITE_GITHUB_ORGS. One variable
  read by both server and client, so the org the settings UI suggests cannot
  drift from the org the server queries. Unset is safe: a fetch reports "no
  organizations configured" instead of rendering an empty list that reads as a
  quiet queue.

Two guide bugs, both self-inflicted:

- The Setup card told users to run `make claude`. No such target exists — it is
  `make run`, which the README already said.
- The drift check that is supposed to catch an undocumented section was itself
  drifting. Its card claimed the `guide` GROUP id while the check reads the
  flattened LEAF list, so the card never rendered and setup/how-to/faq were
  reported undocumented on every load. A card can claim several ids now.

Also corrects the overview table, which omitted the Guide tab and the Claude
sessions panel, and the skill count.

Verified: `pnpm install` resolves, `tsc --noEmit && vite build` passes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@nacholupi nacholupi left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants