fix(vscode): restore codeful bundle version setting

[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 version that the codeful experience should be tied to for public preview.

Impact of Change

• Users: Codeful Logic Apps users get the latest public preview dependency assets/settings on the hotfix branch.
• Developers: No API changes.
• System: Updates bundled VS Code extension dependency assets and removes private extension bundle settings for codeful local settings.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in: git diff --check origin/hotfix/v5.961...HEAD; pinned Biome check on changed TypeScript files

Contributors

Screenshots/Videos

N/A

[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): restore codeful bundle version setting
• Issue: None. The title is specific, concise, and clearly describes the change.
• Recommendation: No change needed.

---

✅ Commit Type

• Properly selected (fix).
• Only one commit type is selected, which is correct.

---

⚠️ Risk Level

• The selected risk level is Low, which is reasonable for this scoped settings change.
• Advised risk remains low based on the diff; no higher risk classification is necessary.

---

✅ What & Why

• Current: Updating the version that the codeful experience should be tied to for public preview.
• Issue: None; brief but sufficient.
• Recommendation: No change needed.

---

✅ Impact of Change

• The impact section is clear and aligned with the diff.
• Recommendation:
  • Users: Good as written.
  • Developers: Good as written.
  • System: Good as written.

---

✅ Test Plan

• Automated tests are present in the diff, including updated unit tests.
• This satisfies the test-plan requirement; the checked manual test note is also acceptable.

---

✅ Contributors

• Blank is acceptable.
• No action required.

---

✅ Screenshots/Videos

• N/A is acceptable for this non-visual change.

---

Summary Table

Section	Status	Recommendation
Title	✅	No change needed
Commit Type	✅	Correctly selected fix
Risk Level	✅	Low is appropriate
What & Why	✅	Sufficiently described
Impact of Change	✅	Good as written
Test Plan	✅	Unit tests were added/updated in the diff
Contributors	✅	Blank is acceptable
Screenshots/Videos	✅	N/A is acceptable

---

The PR passes review. The advised risk level is not higher than the submitter's estimate.

---

Last updated: Mon, 01 Jun 2026 22:38:29 GMT