fix(vscode): Update dependencies to latest for codeful public preview

[lambrianmsft]

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

Updating the sdk and lsp server to have the latest versions required for codeful workflows. These changes are all for public preview. There is no impact on other features.

Impact of Change

• Users:
  Users will see additional supported actions for codeful workflows and all customers can now access it.
• Developers:
  N/A
• System:
  N/A

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:
  VSIX was manually built and tested with these new changes, ensuring that the latest sdk is reflected and the actions are available.

Contributors

@andrew-eldridge

Screenshots/Videos

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 500

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 504

[Copilot]

Pull request overview

This pull request refreshes Graphify knowledge-graph artifacts under graphify-out/ for multiple packages, updating the generated GRAPH_REPORT.md format (including “Graph Freshness”) and revising the reported graph structure (nodes/edges/communities) accordingly.

Changes:

• Regenerated Graphify GRAPH_REPORT.md outputs (new header format + “Graph Freshness” section).
• Updated reported community and “God Node” summaries for several libraries.
• Updated the chatbot Graphify graph.json artifact alongside its report.

Reviewed changes

Copilot reviewed 5 out of 18 changed files in this pull request and generated 9 comments.

Show a summary per file

File	Description
libs/vscode-extension/src/graphify-out/GRAPH_REPORT.md	Regenerated report with new “Graph Freshness” section and updated graph/community summaries.
libs/data-mapper-v2/src/graphify-out/GRAPH_REPORT.md	Regenerated report with new format and updated graph statistics/sections.
libs/chatbot/src/graphify-out/GRAPH_REPORT.md	Regenerated report with new format and updated community listings.
libs/chatbot/src/graphify-out/graph.json	Updated generated graph JSON artifact (commit-stamped).
libs/a2a-core/src/graphify-out/GRAPH_REPORT.md	Regenerated report with new format and updated community/navigation content.

Comments suppressed due to low confidence (1)

libs/a2a-core/src/graphify-out/GRAPH_REPORT.md:22

• The Community Hubs navigation includes a link to "Community 0", but there is no corresponding "### Community 0" section in this report (broken link). Please regenerate so navigation only includes communities that are actually present, or add the missing community section(s).

## Community Hubs (Navigation)
- [[_COMMUNITY_Community 0|Community 0]]
- [[_COMMUNITY_Community 1|Community 1]]
- [[_COMMUNITY_Community 2|Community 2]]
- [[_COMMUNITY_Community 3|Community 3]]
- [[_COMMUNITY_Community 4|Community 4]]

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 500

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: fix(vscode): Update dependencies to latest for codeful public preview
• Issue: Title is generally good but could be more specific about which dependencies were updated (LSP server, workflows SDK, removed pinned extension bundle settings).
• Recommendation: Be explicit about the main artifacts changed. Example: fix(vscode): Update LSP server and Workflows SDK, remove pinned extension bundle for codeful public preview

---

✅ Commit Type

• Properly selected (fix).
• Note: Only one commit type selected which is correct for this change.

---

⚠️ Risk Level

• Assessment: The PR body marks this as Low and the repo has the risk:low label. However, the code diff replaces LSP server binary and a Workflows SDK package and removes pinned extension bundle settings — changes that affect runtime behavior for codeful workflows and shipped assets.
• Recommendation: Update the PR risk to Medium (and change the label to risk:medium) because shipping different LSP server / SDK binaries and removing pinned versioning can cause compatibility or runtime issues for users.

---

✅ What & Why

• Current: "Updating the sdk and lsp server to have the latest versions required for codeful workflows. These changes are all for public preview. There is no impact on other features."
• Issue: Clear and concise but could call out which exact packages/binaries were updated and why (e.g., bugfixes, new features required for codeful support).
• Recommendation: Expand with one line listing the main artifacts changed (LSPServer.zip, Microsoft.Azure.Workflows.Sdk.1.0.0-preview.1.nupkg, removal of pinned extension bundle entries).

---

⚠️ Impact of Change

• Issue: The PR lists Users and marks Developers/System as N/A. Because you changed shipped assets and removed pinned extension bundle settings, there is potential developer and system impact that should be documented.
• Recommendation:
  • Users: Users of the VS Code extension / codeful workflows may see additional supported actions and should be told to upgrade their VSIX. Also note any potential breaking behavior (if known).
  • Developers: Mention that extension binaries/assets were updated (LSP server and SDK) and that local settings behavior changed (removed pinned extension bundle/version), which can affect local dev/debug setups.
  • System: Note any performance, packaging, or CI/packaging impacts (e.g., new binary sizes, updated packaging step for VSIX, or dependency hosting changes).

---

✅ Test Plan

• Assessment: Manual testing completed and VSIX was built and tested as described. The code diff contains binary updates and no unit/E2E tests were added.
• Recommendation: If possible, add an automated smoke or integration test covering basic LSP/SDK functionality or include a short checklist of manual test steps and environments (VS Code version, OS tested). If adding automated tests isn’t feasible for the binary assets, document why and include the manual verification steps and expected outcomes clearly in the PR body.

---

✅ Contributors

• Assessment: Contributors section present (@andrew-eldridge). Good practice.

---

✅ Screenshots/Videos

• Assessment: Not applicable for this change (no UI visuals changed). OK to leave blank.

---

Summary Table

Section	Status	Recommendation
Title	✅	Make title slightly more specific about artifacts updated
Commit Type	✅	No change needed
Risk Level	⚠️	Change to Medium and update label to risk:medium
What & Why	✅	Add one line listing exact artifacts changed
Impact of Change	⚠️	Expand Developer/System impact details
Test Plan	✅	Add brief manual test steps or an automated smoke test if possible
Contributors	✅	No change needed
Screenshots/Videos	✅	No change needed

---

Final message
Please update the PR to reflect the advised risk (Medium) and adjust the risk label accordingly. Also expand the What & Why section to list the updated artifacts (LSPServer.zip, Microsoft.Azure.Workflows.Sdk.1.0.0-preview.1.nupkg, removal of extension bundle settings), and provide more detail in Impact of Change (developer and system impacts). Finally, include a short manual test checklist and environments you validated, or add a small automated smoke/integration test if feasible.

Note: I recommended a higher risk level (Medium) than the PR currently states because replacing shipped LSP/SDK binaries and removing pinned extension bundle/versioning can introduce compatibility or runtime changes that deserve additional scrutiny.

---

Last updated: Wed, 20 May 2026 00:23:09 GMT

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 500

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 500

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 504

[github-actions]

❌ PR Validation Error

An error occurred while validating your PR. Please try again later or contact the maintainers.

Error: API request failed with status 500