Skip to content

[Candidate Intake - Partial] Upstream PR #260 - fix: correct dashboard version checks and Cline integration#7

Draft
nsalvacao wants to merge 3 commits intomasterfrom
upstream-prs/pr-260
Draft

[Candidate Intake - Partial] Upstream PR #260 - fix: correct dashboard version checks and Cline integration#7
nsalvacao wants to merge 3 commits intomasterfrom
upstream-prs/pr-260

Conversation

@nsalvacao
Copy link

@nsalvacao nsalvacao commented Mar 16, 2026

Context

This draft PR mirrors upstream branch 'upstream-prs/pr-260' into 'master' for review, provenance, and later decision-making only.
It must not be merged wholesale. If we adopt anything from it, the intended path is commit-level intake only.

Upstream Source

Current Intake Recommendation

  • Decision: Candidate intake (partial)
  • Status: Planned review only, with no integration performed yet
  • Credit policy: preserve original author metadata, use git cherry-pick -x for any later intake, and keep any conflict adaptation in separate follow-up commits with explicit upstream attribution

Selected Commits For Any Future Intake

  • 33b797d fix(version): stop dashboard from using npm CLI updates

Skipped / Excluded Scope

  • b80111c fix(cline): use workos auth token shape skipped because current master already appears patch-equivalent.
  • 0400bcc fix(cline): refresh static model catalog skipped because current master already appears patch-equivalent.

Acceptance Gates

  • Do not merge this mirrored branch as-is.
  • If anything is adopted later, intake only the explicitly selected commits or a newly re-validated subset.
  • Preserve upstream authorship and provenance in Git history.
  • Keep conflict-resolution/adaptation commits separate from upstream-authored commits.
  • Reconfirm branch contents against current master at intake time before changing the selected scope.

Verification / Validation Checklist

  • Dashboard version check no longer depends on npm CLI update behavior.
  • Existing Cline behavior remains stable with only the selected commit considered.
  • No new noisy update prompts or regressions appear in the dashboard.

Review Focus

  • Dashboard version check behavior without shelling through npm updates
  • Whether the skipped Cline commits truly remain redundant today

Notes

  • This is a partial-intake candidate. Only the selected version-check fix is currently in scope.
  • The two Cline-related commits remain documented here but are presently considered already absorbed.

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