Release v4.14 (#674)

## 🎯 Aim

The aim is to create a new minor release with the latest enhancements. 

## 📷 Result

<img width="317" height="517"
alt="{AC614884-F989-42E0-B331-3B59BFEDABD0}"
src="https://github.com/user-attachments/assets/a61b472f-a4db-4f03-9a9b-68364d6ca6a2"
/>

<img width="802" height="505"
alt="{E31153EB-433D-4ABA-8BE9-D4D79938B41D}"
src="https://github.com/user-attachments/assets/0e6157ab-5b8b-4c78-96aa-934d5de971d6"
/>

<img width="851" height="510"
alt="{F3A4E8FB-76BA-45D1-B29A-E28DA384FC9A}"
src="https://github.com/user-attachments/assets/b75b8d60-1671-4aec-bd5e-2218668df36c"
/>

<img width="991" height="504"
alt="{62074708-6BA4-4A4F-9C4B-9B68868ED1F7}"
src="https://github.com/user-attachments/assets/8ef1ea6d-c5d8-43a0-aeb0-8d85f98d47cf"
/>


## ✅ What was done

- [x] Added Support for SPFx 1.22.0 and 1.22.1
- [x] Added preferred node package manager setting
- [x] Added Heft tasks view
- [x] Added remove_spo_page language model tool for SharePoint
- [x] Added get_spo_page language model tool for SharePoint
- [x] Added list_spo_page language model tool for modern SharePoint page
listing
- [x] Added support for all SPFx versions to upgrade action and language
model upgrade project tool
- [x] Fixed bug with publish solution
- [x] Extended copilot- [x]instructions
- [x] Refactored spo_list_get language model tool
- [x] Refactored spo_list_add language model tool
- [x] Refactored spo_list_remove language model tool
- [x] Fixed Toolkit getting stuck during component creation if `yo` is
not installed
- [x] Updated Contribution guidelines
- [x] Refactored the way we add CLI for Microsoft 365 to SPFx Toolkit
- [x] Updated install dependencies and validate local setup to support
all SPFx versions
- [x] Added Timezone Dropdown for Tenant App Catalog Creation
- [x] Added Feedback form
- [x] Added npm scripts as part of Tasks view
- [x] Fixed sample gallery script
- [x] Added link for CLI for Microsoft 365 MCP server in the help and
feedback section
- [x] Improved model description for list_spo_app, install_spo_app
language model tools
- [x] Enhanced list_spo_app to support listing apps from site collection
app catalog
- [x] Enhanced install_spo_app to install app from site level app
catalog
- [x] Added new uninstall_spo_app language model tools
- [x] Added new upgrade_spo_app language model tool
- [x] Added new list_spo_app_instances language model tool

---------

Co-authored-by: Saurabh Tripathi <saurabh7019@gmail.com>
Co-authored-by: Nico De Cleyre <35696168+nicodecleyre@users.noreply.github.com>
Co-authored-by: Harshith Sai V <68597202+harshithsaiv@users.noreply.github.com>
Co-authored-by: Nirav Raval <niravraval34@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>

Author: 7 people

.github/copilot-instructions.md

@@ -11,6 +11,28 @@ This is a **VS Code extension** that serves as an **abstraction layer** over the
 - **Service Layer**: Abstraction over CLI for Microsoft 365 commands
 - **Authentication**: Microsoft 365 authentication via `AuthProvider`
 
+## Key Constraints
+
+### Contribution Workflow
+- Always review `contributing.md` before starting work to understand the workflow, branching strategy, PR requirements, and documentation updates
+- Create feature/fix branches from `dev` branch (never from `main`)
+- Target all PRs to `dev` branch (PRs targeting `main` will be declined)
+- PRs must include summary, linked issue (if applicable), and testing steps
+- Update relevant documentation in `/docs` folder when making changes
+- Use descriptive commit messages that reference issue numbers (e.g., `fixes #123`)
+
+### Dependency Management
+- Do not add entries to `package.json` as new dependencies require maintainer evaluation and manual approval
+- Do not modify `npm-shrinkwrap.json` as lock files are regenerated after dependency changes via `npm install`
+- If resolving an issue requires a new npm package:
+  - Create a draft PR with a comment explaining which dependency is needed, why, and what alternatives were considered
+  - Do not attempt workarounds that duplicate functionality available in potential dependencies
+- Work within the constraints of existing dependencies whenever possible
+
+### Security and Privacy
+- Never embed secrets, tokens, or credentials in code or docs
+- If an issue requires sensitive information (API keys, tokens, credentials) create a draft PR explaining what configuration is needed and flag it for manual setup by maintainers
+
 ## Development Workflow
 
 ### Build System
@@ -68,10 +90,11 @@ npm run test           # Run VS Code extension tests
 
 ### Language Model Tools
 The extension exposes SharePoint Online operations as GitHub Copilot tools:
-- `spo_app_list`, `spo_app_install` - App catalog management
-- `spo_list_add`, `spo_list_get`, `spo_list_remove` - List operations
-- `spo_page_add` - Page creation
+- `list_spo_app`, `install_spo_app`, `uninstall_spo_app`, `upgrade_spo_app`, `list_spo_app_instances` - App catalog management
+- `add_spo_list`, `get_spo_list`, `remove_spo_list` - List operations
+- `add_spo_page` - Page creation
 - `spo_site_add`, `spo_site_get`, `spo_site_remove` - Site management
+- `upgrade_spfx_project` - SPFx project upgrade
 
 ## Development Conventions
 

.github/workflows/check-tests.yml

@@ -26,33 +26,9 @@ jobs:
           path: vscode-viva
 
       - name: Install dependencies for SPFx Toolkit
-        run: npm ci
+        run: npm install --omit=optional
         working-directory: vscode-viva
 
-      - name: Checkout CLI for Microsoft 365
-        uses: actions/checkout@v4
-        with:
-          repository: Adam-it/cli-microsoft365
-          path: cli-microsoft365
-          ref: cli-cjs
-
-      - name: Print dir
-        run: |
-          dir
-
-      - name: Install dependencies for CLI for Microsoft 365
-        run: npm i
-        working-directory: cli-microsoft365
-
-      - name: Build CLI for Microsoft 365
-        run: npm run build
-        working-directory: cli-microsoft365
-
-      - name: Run script to copy local CLI for Microsoft 365   
-        run: .\vscode-viva\scripts\cli-for-microsoft365-copy-local-version.ps1 -workspacePath "${{ github.workspace }}"
-        shell: pwsh
-        continue-on-error: false
-
       - name: Build SPFx Toolkit
         run: npm run package
         working-directory: vscode-viva

.github/workflows/release-beta.yml

@@ -26,33 +26,9 @@ jobs:
           path: vscode-viva
 
       - name: Install the dependencies
-        run: npm ci
+        run: npm install --omit=optional
         working-directory: vscode-viva
 
-      - name: Checkout cli-microsoft365
-        uses: actions/checkout@v4
-        with:
-          repository: Adam-it/cli-microsoft365
-          path: cli-microsoft365
-          ref: cli-cjs
-
-      - name: Print dir
-        run: |
-          dir
-
-      - name: Restore dependencies for cli-microsoft365
-        run: npm i
-        working-directory: cli-microsoft365
-
-      - name: Build cli-microsoft365
-        run: npm run build
-        working-directory: cli-microsoft365
-
-      - name: Run script copy local CLI for M365    
-        run: .\vscode-viva\scripts\cli-for-microsoft365-copy-local-version.ps1 -workspacePath "${{ github.workspace }}"
-        shell: pwsh
-        continue-on-error: false
-
       - name: Publish 
         run: npx @vscode/vsce@3.3.2 publish -p ${{ secrets.VSCE_PAT }} --pre-release --baseImagesUrl https://raw.githubusercontent.com/pnp/vscode-viva/dev
         working-directory: vscode-viva

.github/workflows/release-local.yml

@@ -25,33 +25,9 @@ jobs:
           path: vscode-viva
 
       - name: Install the dependencies
-        run: npm ci
+        run: npm install --omit=optional
         working-directory: vscode-viva
 
-      - name: Checkout cli-microsoft365
-        uses: actions/checkout@v4
-        with:
-          repository: Adam-it/cli-microsoft365
-          path: cli-microsoft365
-          ref: cli-cjs
-
-      - name: Print dir
-        run: |
-          dir
-
-      - name: Restore dependencies for cli-microsoft365
-        run: npm i
-        working-directory: cli-microsoft365
-
-      - name: Build cli-microsoft365
-        run: npm run build
-        working-directory: cli-microsoft365
-
-      - name: Run script copy local CLI for M365    
-        run: .\vscode-viva\scripts\cli-for-microsoft365-copy-local-version.ps1 -workspacePath "${{ github.workspace }}"
-        shell: pwsh
-        continue-on-error: false
-
       - name: Package
         run: |
           npx @vscode/vsce@3.3.2 package

.github/workflows/release.yml

@@ -29,33 +29,9 @@ jobs:
           path: vscode-viva
 
       - name: Install the dependencies
-        run: npm ci
+        run: npm install --omit=optional
         working-directory: vscode-viva
 
-      - name: Checkout cli-microsoft365
-        uses: actions/checkout@v4
-        with:
-          repository: Adam-it/cli-microsoft365
-          path: cli-microsoft365
-          ref: cli-cjs
-
-      - name: Print dir
-        run: |
-          dir
-
-      - name: Restore dependencies for cli-microsoft365
-        run: npm i
-        working-directory: cli-microsoft365
-
-      - name: Build cli-microsoft365
-        run: npm run build
-        working-directory: cli-microsoft365
-
-      - name: Run script copy local CLI for M365    
-        run: .\vscode-viva\scripts\cli-for-microsoft365-copy-local-version.ps1 -workspacePath "${{ github.workspace }}"
-        shell: pwsh
-        continue-on-error: false
-
       - name: Publish
         run: npx @vscode/vsce@3.3.2 publish -p ${{ secrets.VSCE_PAT }}
         working-directory: vscode-viva

CHANGELOG.md

@@ -1,5 +1,35 @@
 # Change Log
 
+## [4.14.0] - 2025-12-18
+
+- Added Support for SPFx 1.22.0 and 1.22.1
+- Added preferred node package manager setting
+- Added Heft tasks view
+- Added remove_spo_page language model tool for SharePoint
+- Added get_spo_page language model tool for SharePoint
+- Added list_spo_page language model tool for modern SharePoint page listing
+- Added support for all SPFx versions to upgrade action and language model upgrade project tool
+- Fixed bug with publish solution
+- Extended copilot-instructions
+- Refactored spo_list_get language model tool
+- Refactored spo_list_add language model tool
+- Refactored spo_list_remove language model tool
+- Fixed Toolkit getting stuck during component creation if `yo` is not installed
+- Updated Contribution guidelines
+- Refactored the way we add CLI for Microsoft 365 to SPFx Toolkit
+- Updated install dependencies and validate local setup to support all SPFx versions
+- Added Timezone Dropdown for Tenant App Catalog Creation
+- Added Feedback form
+- Added npm scripts as part of Tasks view
+- Fixed sample gallery script
+- Added link for CLI for Microsoft 365 MCP server in the help and feedback section
+- Improved model description for list_spo_app, install_spo_app language model tools
+- Enhanced list_spo_app to support listing apps from site collection app catalog
+- Enhanced install_spo_app to install app from site level app catalog
+- Added new uninstall_spo_app language model tools
+- Added new upgrade_spo_app language model tool
+- Added new list_spo_app_instances language model tool
+
 ## [4.12.0] - 2025-10-07
 
 - Compressed images in extension and docs

README.md

@@ -68,15 +68,11 @@ To ensure that you can develop SPFx solutions, you may use the **Validate local
 
 ![Validate dependency](./docs/assets/images-vscode/validate-dependency.png)
 
-This action will check if you have the required dependencies such as:
+This action checks if your local development environment meets the required versions of Node.js and global dependencies for the SPFx version you have installed, and in case you do not have any SPFx generator installed, it will validate against the latest SPFx version.
 
-- Node version: 22
-- NPM dependencies:
-  - gulp
-  - yo
-  - @microsoft/generator-sharepoint
+It is also possible to install the required Node.js version and global dependencies for any SPFx version using the **Install dependencies** action.
 
-In case you do not have all dependencies installed, or some are incorrect version, you can use the **install dependencies** action to install them.
+![install dependencies](./assets/images/install-dependencies.png)
 
 >  [!NOTE]
 >  The list of valid dependencies is based on [set up your development environment recommendations](https://learn.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment)
@@ -185,12 +181,18 @@ Sign-in is also required for some actions to work properly like the deploy actio
 
 [Check out our docs for more details](https://pnp.github.io/vscode-viva/features/sign-in)
 
-### 7️⃣ Gulp tasks
+### 7️⃣ Tasks
 
-The extension shows all possible Gulp tasks one may run on an SPFx project. The tasks allow you to clean, bundle, package, serve the project with a single click.
+The extension shows all possible tasks that can be run on an SPFx project. The tasks view displays all relevant tasks available for the current SPFx project, as well as all npm scripts defined in the `package.json` file.
+
+For SPFx projects created with versions below 1.22, Gulp tasks will be shown in the tasks view:
 
 ![Gulp Tasks](./docs/assets/images-vscode/tasks.png)
 
+For SPFx projects created with version 1.22 and above, Heft tasks will be shown in the tasks view:
+
+![Tasks](./docs/assets/images-vscode/heft-tasks.png)
+
 [Check out our docs for more details](https://pnp.github.io/vscode-viva/features/coding#gulp-tasks-view)
 
 ### 8️⃣ Actions
@@ -215,7 +217,7 @@ And for Azure DevOps👇
 
 [Check out our docs for more details](https://pnp.github.io/vscode-viva/features/ci-cd)
 
-- **Upgrade project** - Uses CLI for Microsoft 365 to create a .md and/or code tour report with upgrade guidance to the latest supported SPFx version by the extension. The upgrade guidance provides optional as well as required steps a user needs to take manually in order to upgrade the project. At the end of the guidance file, the user may find a summary of the steps in a single script and a couple of manual steps that need to be taken.
+- **Upgrade project** - Generates a detailed upgrade report (`.md` and/or code tour) to guide users from their current SPFx version to a selected target version using CLI for Microsoft 365. The report includes both required and optional upgrade steps, with a consolidated script at the end for automated actions and a list of remaining manual steps.
 
 ![Upgrade project](./docs/assets/images-vscode/upgrade-project.png)
 

assets/walkthrough/actions.md

@@ -18,9 +18,9 @@ And for Azure DevOps👇
 
 ![Azure DevOps CI CD pipeline](../../docs/assets/images-vscode/azdo-ci-cd.gif)
 
-[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#cicd-workflow)
+[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/ci-cd/)
 
-- **Upgrade project** - Uses CLI for Microsoft 365 to create a .md and/or code tour report with upgrade guidance to the latest supported SPFx version by the extension. The upgrade guidance provides optional as well as required steps a user needs to take manually in order to upgrade the project. At the end of the guidance file, the user may find a summary of the steps in a single script and a couple of manual steps that need to be taken.
+- **Upgrade project** - Generates a detailed upgrade report (`.md` and/or code tour) to guide users from their current SPFx version to a selected target version using CLI for Microsoft 365. The report includes both required and optional upgrade steps, with a consolidated script at the end for automated actions and a list of remaining manual steps.
 
 ![Upgrade project](../../docs/assets/images-vscode/upgrade-project.png)
 

assets/walkthrough/cicd-workflow.md

@@ -14,4 +14,4 @@ And for Azure DevOps👇
 
 ![Azure DevOps CI CD pipeline](../../docs/assets/images-vscode/azdo-ci-cd.gif)
 
-[Check out our docs for more details and a step by step guide](https://pnp.github.io/vscode-viva/features/actions/#cicd-workflow)
+[Check out our docs for more details and a step by step guide](https://pnp.github.io/vscode-viva/features/ci-cd/)

assets/walkthrough/spfx-intro.md

@@ -10,7 +10,7 @@ The following are some of the key features included as part of the SPFx:
 - The controls are responsive and accessible by nature.
 - It enables the developer to access the lifecycle in addition to render, load, serialize and deserialize, configuration changes, and more.
 - It's framework-agnostic. You can use any JavaScript framework that you like including, but not limited to, React, Handlebars, Knockout, Angular, and Vue.js.
-- The developer toolchain is based on popular open-source client development tools such as NPM, TypeScript, Yeoman, webpack, and gulp.
+- The developer toolchain is based on popular open-source client development tools such as NPM, TypeScript, Yeoman, webpack, and heft/gulp.
 - Performance is reliable.
 - End users can use SPFx client-side solutions that are approved by the tenant administrators (or their delegates) on all sites, including self-service team, group, or personal sites.
 - SPFx web parts can be added to both classic and modern pages.