Docs: align Node.js version to >=20 LTS - #305
Merged
bradygaster merged 2 commits intoMar 10, 2026
Merged
Conversation
package.json engines requires >=20.0.0 but docs referenced v22 in 5 places. Updated all to Node.js 20+ (LTS) with nvm --lts install commands instead of pinned versions. Files: docs/README.md, guide.md, troubleshooting.md, vscode.md Closes bradygaster#302 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
diberry
commented
Mar 9, 2026
diberry
left a comment
diberry
left a comment
Contributor
Author
There was a problem hiding this comment.
✅ Approved — Clean version alignment across all docs.
Microsoft Style Guide compliance: ✅
- All changes maintain sentence-case, active voice, second person
- No style regressions introduced
Technical accuracy: ✅
- Node.js 20+ (LTS) is correct — aligns with package.json engines field
- All 4 files updated consistently (docs/README.md, features/vscode.md, guide.md, scenarios/troubleshooting.md)
- nvm examples updated to use LTS flags instead of hardcoded versions
Tone: ✅
- No tone changes, purely technical updates
- "LTS" clarification adds helpful context
Navigation: ✅
- No navigation changes (editing existing content)
DOCS-TEST SYNC: ✅ Not required
This PR updates version references in existing docs, not adding new pages. No test updates needed.
Excellent hygiene. Version consistency matters.
— PAO
diberry
added a commit
to diberry/squad
that referenced
this pull request
Mar 9, 2026
… recommendations Session: 2026-03-09T19-16-49Z-docs-consolidation Requested by: Copilot (Scribe role) Changes: - Merged 5 inbox decisions (user directives, McManus docs audit, Keaton config audit) - Updated decisions.md with progressive disclosure framework and docs work classification - Appended cross-agent team updates to PAO, FIDO, Procedures history files - Cleared decision inbox (5 files removed) Summary: - PAO approved all 4 docs PRs (bradygaster#318, bradygaster#317, bradygaster#305, bradygaster#303) with docs-test sync verified - FIDO validated test assertions for 4 new docs files (EXPECTED_CONCEPTS array correct, no gaps) - Procedures approved human-members.md template PR bradygaster#315 - 44-issue docs backlog now configured with routing, ceremonies, skills, and @copilot capability profile - Team aligned on progressive disclosure and documentation conventions Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
@bradygaster — This PR is ready for your review. CI is green. 🚀 |
Ab3y
pushed a commit
to Ab3y/squad
that referenced
this pull request
Mar 10, 2026
…ygaster#305) - Trigger on v* tag push or manual workflow_dispatch with version input - Publishes squad-sdk first, then squad-cli (respecting dependency order) - Uses npm publish --provenance for supply chain security - Creates GitHub Release with auto-generated release notes - Uses GITHUB_TOKEN for release creation, NPM_TOKEN for npm publishing - Replaces need for separate tag creation in publish workflow Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Ab3y
pushed a commit
to Ab3y/squad
that referenced
this pull request
Mar 10, 2026
…ire-and-watcher feat: OTel Phase 4 — Aspire command, file watcher, event payloads, CI/CD (bradygaster#265, bradygaster#268, bradygaster#304, bradygaster#305)
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
2 participants
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.
Problem
\package.json\ engines field requires >=20.0.0, but 5 places in the docs referenced Node.js 22. This confused new users who had Node 20 installed and thought they needed to upgrade.
Changes
Updated all 5 references across 4 files:
Also changed nvm commands from
vm install 22\ to
vm install --lts\ so they stay evergreen.
Closes #302
cc @bradygaster