Skip to content

Commit 6a96534

Browse files
Adam-itCopilotSaurabh7019NishkalankBezawadanirav-raval
authored
Release v4.8.0 (#508)
## 🎯 Aim The aim is to create a new minor release with the latest enhancements. ## 📷 Result gulp task icons ![image](https://github.com/user-attachments/assets/2dab9fd1-13b8-4bb8-bd2f-4b986daf2ff3) default SPFx app action set to install ![image](https://github.com/user-attachments/assets/66e7ca4e-a8aa-4001-b082-702c2c2a8ba9) LM tools ![image](https://github.com/user-attachments/assets/696ca088-4209-4930-829e-2d76a86a3544) node.js version support ![image](https://github.com/user-attachments/assets/b92d0148-e961-489f-8b38-f0d519e83e17) add remove site level app catalogs ![image](https://github.com/user-attachments/assets/cb670433-2804-48c2-9a4d-d8ad27251738) renames /manage to /info chat command ![image](https://github.com/user-attachments/assets/f3af41a7-9ed2-45c4-b379-b613764add2b) ## ✅ What was done - [X] Added LLM Tools for GitHub Copilot agent mode - [X] Hidden app management related context-menu actions from the command pallete - [X] Added support for installing the correct version of Node.js - [X] Fixed setting form customizer list from to root site - [X] Updated command category names to shorten version - [X] Updated default action for SPFx app to install - [X] Renamed the /manage chat command to /info - [X] Added gulp operations to VS Code extension commands - [X] Updated gulp tasks icons - [X] Updated Teams Toolkit to M365 Agents Toolkit - [X] Updated wiki link to a new name and URL - [X] Updated Dependencies - [X] Added features to add tenant app catalog and add/remove site app catalog - [X] Added progress notification for SPFx actions - [X] Added upgrade suggestion in case installation fails due to app being already installed --------- Co-authored-by: Copilot <[email protected]> Co-authored-by: Saurabh Tripathi <[email protected]> Co-authored-by: Nishkalank Bezawada <[email protected]> Co-authored-by: Nirav Raval <[email protected]> Co-authored-by: Nico De Cleyre <[email protected]>
1 parent 04befb3 commit 6a96534

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

65 files changed

+5139
-3024
lines changed

.eslintrc.json

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
],
1111
"rules": {
1212
"@typescript-eslint/naming-convention": "off",
13-
"@typescript-eslint/semi": "warn",
13+
"@typescript-eslint/semi": "off",
1414
"no-compare-neg-zero": "error",
1515
"no-cond-assign": "error",
1616
"no-const-assign": "error",
@@ -23,7 +23,6 @@
2323
"curly": "error",
2424
"eqeqeq": "error",
2525
"no-throw-literal": "warn",
26-
"semi": "error",
2726
"no-extra-semi": "error",
2827
"no-console": "error",
2928
"no-else-return": "error",

.github/workflows/release-beta.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,6 @@ jobs:
5353
shell: pwsh
5454
continue-on-error: false
5555

56-
- name: Publish
57-
run: npx @vscode/vsce@2.30.0 publish -p ${{ secrets.VSCE_PAT }} --pre-release --baseImagesUrl https://raw.githubusercontent.com/pnp/vscode-viva/dev
56+
- name: Publish
57+
run: npx @vscode/vsce@3.3.2 publish -p ${{ secrets.VSCE_PAT }} --pre-release --baseImagesUrl https://raw.githubusercontent.com/pnp/vscode-viva/dev
5858
working-directory: vscode-viva

.github/workflows/release-local.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ jobs:
5454

5555
- name: Package
5656
run: |
57-
npx @vscode/vsce@2.30.0 package
57+
npx @vscode/vsce@3.3.2 package
5858
working-directory: vscode-viva
5959

6060
- name: Upload artifacts

.github/workflows/release.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,5 +57,5 @@ jobs:
5757
continue-on-error: false
5858

5959
- name: Publish
60-
run: npx @vscode/vsce@2.30.0 publish -p ${{ secrets.VSCE_PAT }}
60+
run: npx @vscode/vsce@3.3.2 publish -p ${{ secrets.VSCE_PAT }}
6161
working-directory: vscode-viva

CHANGELOG.md

Lines changed: 25 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
11
# Change Log
22

3+
## [4.8.0] - 2025-06-07
4+
5+
- Added LLM Tools for GitHub Copilot agent mode
6+
- Hidden app management related context-menu actions from the command pallete
7+
- Added support for installing the correct version of Node.js
8+
- Fixed setting form customizer list from to root site
9+
- Updated command category names to shorten version
10+
- Updated default action for SPFx app to install
11+
- Renamed the /manage chat command to /info
12+
- Added gulp operations to VS Code extension commands
13+
- Updated gulp tasks icons
14+
- Updated Teams Toolkit to M365 Agents Toolkit
15+
- Updated wiki link to a new name and URL
16+
- Updated Dependencies
17+
- Added features to add tenant app catalog and add/remove site app catalog
18+
- Added progress notification for SPFx actions
19+
- Added upgrade suggestion in case installation fails due to app being already installed
20+
321
## [4.7.0] - 2025-05-04
422

523
- Added support for SPFx 1.21.1
@@ -10,13 +28,13 @@
1028

1129
## [4.5.0] - 2025-04-14
1230

13-
- Adds new Gulp task Publish, which includes both bundle and package
14-
- Updates settings to allow not to load apps for app catalogs
15-
- Updates serve gulp tasks to combine them into a single task
16-
- Refactors pipeline scaffolding form to smaller components
17-
- Adds initial integration tests for the product
18-
- Add an action that allows to increase project version and implement version increment logic
19-
- Fixes App Install/Uninstall issue to allow installing apps on root site
31+
- Added new Gulp task Publish, which includes both bundle and package
32+
- Updated settings to allow not to load apps for app catalogs
33+
- Updated serve gulp tasks to combine them into a single task
34+
- Refactored pipeline scaffolding form to smaller components
35+
- Added initial integration tests for the product
36+
- Added an action that allows to increase project version and implement version increment logic
37+
- Fixed App Install/Uninstall issue to allow installing apps on root site
2038

2139
## [4.4.0] - 2025-02-04
2240

README.md

Lines changed: 38 additions & 28 deletions
Large diffs are not rendered by default.

assets/images/better-together.png

64.8 KB
Loading
-3.83 MB
Binary file not shown.
47.9 KB
Loading
67 KB
Loading

assets/images/scaffolding.png

-17.4 KB
Loading

assets/images/tasks.png

3.42 KB
Loading

assets/images/validate-dependency.png

-19.4 KB
Loading

assets/images/welcome-experience.png

-93.2 KB
Loading

assets/walkthrough/actions.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Actions
1+
# Actions
22

33
The actions section allows unique functionalities that may significantly boost productivity when working with SPFx projects.
44

@@ -18,60 +18,60 @@ And for Azure DevOps👇
1818

1919
![Azure DevOps CI CD pipeline](../images/azdo-ci-cd.gif)
2020

21-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#cicd-github-workflow)
21+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#cicd-workflow)
2222

2323
- **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.
2424

2525
![Upgrade project](../images/upgrade-project.png)
2626

2727
And the code tour guidance will provide you upgrade tips directly in your code!
2828

29-
![Upgrade project](./assets/images/upgrade-project-code-tour.png)
29+
![Upgrade project](../images/upgrade-project-code-tour.png)
3030

31-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#upgrade-project)
31+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#upgrade-project)
3232

3333
- **Validate project** - Creates a validation .md report and/or code tour validation guidance for the currently open SPFx project. The action will automatically detect the SPFx version used and will validate if the project is properly set up.
3434

3535
![Upgrade project](../images/validate-project.png)
3636

37-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#validate-current-project)
37+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#validate-current-project)
3838

3939
- **Rename project** - Forget about manual work and let the extension rename your project and generate a new solution ID.
4040

4141
![Rename](../images/rename.png)
4242

43-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#rename-current-project)
43+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#rename-current-project)
4444

4545
- **Grant API permissions** - The action will Grant all API permissions specified in the package-solution.json of the current project. This is especially helpful if you just want to debug your SPFx solution using Workbench. No longer do you need to bundle, package, and deploy the project to then go to the SharePoint admin portal and consent to the permissions. All of that is now done with just a single click.
4646

4747
![Grant permissions](../images/grant-permissions.png)
4848

49-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#grant-api-permissions)
49+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#grant-api-permissions)
5050

5151
- **Deploy project** - This action will only work when the user is logged in to tenant and the sppkg file is present. The action will deploy the project to the selected (tenant or site) app catalog.
5252

5353
![Deploy](../images/deploy.png)
5454

55-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#grant-api-permissions)
55+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#deploy-project)
5656

5757
- **Add new component** - Allows scaffolding a new SPFx project as a new component of the currently opened project. The action under the hood uses the same SharePoint Yeoman generator to scaffold a new project and this feature is an abstraction UI layer.
5858

5959
![Add component](../images/add-component.png)
6060

61-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#add-new-component)
61+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#add-new-component)
6262

6363
- **Set Form Customizer** - Allows to update the New, Edit or View from of any SharePoint List to a given SPFx Form Customizer based on provided GUID.
6464

6565
![Set Form Customizer](../images/set-form-customizer-action.png)
6666

67-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#set-form-customizer)
67+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#set-form-customizer)
6868

69-
- **Increase project version** - This action allows you to increase project major, minor or patch varsion and automatically align the versioning between `package.json` and `package-solution.json` files.
69+
- **Increase project version** - This action allows you to increase project major, minor or patch version and automatically align the versioning between `package.json` and `package-solution.json` files.
7070

7171
![Increase project version](../images/increase-versioning.png)
7272

73-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#increase-project-version)
73+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#increase-project-version)
7474

7575
- **Open sample/scenario galleries of the SPFx web part, extensions, or ACEs projects** - SharePoint Framework Toolkit supports a couple of sample galleries that may be used to scaffold a new SPFx project.
7676

77-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#open-samplescenario-galleries-of-the-spfx-web-part-extensions-or-aces-projects)
77+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/actions/#open-samplescenario-galleries-of-the-spfx-web-part-extensions-or-aces-projects)

assets/walkthrough/cicd-workflow.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
## CI/CD Workflow
1+
# CI/CD Workflow
22

33
SharePoint Framework Toolkit extends VS Code with additional UI to present you with a scaffolding form that will allow you to create a CI/CD Workflow in 3 easy steps.
44

5-
It's important to know that many fields are already prefield and it is possible to hit create without changing any value to get a basic and default YAML workflow file.
5+
It's important to know that many fields are already pre-filled and it is possible to hit create without changing any value to get a basic and default YAML workflow file.
66

77
![CI CD pipeline](../images/CICD-pipeline.png)
88

@@ -14,4 +14,4 @@ And for Azure DevOps👇
1414

1515
![Azure DevOps CI CD pipeline](../images/azdo-ci-cd.gif)
1616

17-
[Check out our docs for more details and a step by step guide](https://github.com/pnp/vscode-viva/wiki/5.5-Actions#cicd-github-workflow)
17+
[Check out our docs for more details and a step by step guide](https://pnp.github.io/vscode-viva/features/actions/#cicd-workflow)

assets/walkthrough/coding-snippets.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
## Coding Snippets
1+
# Coding Snippets
22

3-
The SharePoint Framework Toolkit comes together as a bundle with two other extensions. One of them is [SPFx Snippets](https://marketplace.visualstudio.com/items?itemName=eliostruyf.spfx-snippets) created by [Elit Struyf](https://www.eliostruyf.com/).
3+
The SharePoint Framework Toolkit comes together as a bundle with two other extensions. One of them is [SPFx Snippets](https://marketplace.visualstudio.com/items?itemName=eliostruyf.spfx-snippets) created by [Elio Struyf](https://www.eliostruyf.com/).
44

55
It contains snippets for working in:
66

assets/walkthrough/create-new-project.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
## Create a new project
1+
# Create a new project
22

3-
Creating a new project was never easier. Just use the **create a new project** action, and the extension will guide you through the process with a dedicated scaffolding form.
3+
Creating a new project has never been easier. Just use the **create a new project** action, and the extension will guide you through the process with a dedicated scaffolding form.
44

55
![Create new project](../images/scaffolding.png)
66

@@ -17,7 +17,7 @@ Install additional dependencies with a single click straight from the scaffoldin
1717

1818
![Additional dependency step](../images/scaffolding-additional-step.png)
1919

20-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.2-Scaffolding#1-scaffold-a-new-spfx-project)
20+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/scaffolding/#1-scaffold-a-new-spfx-project)
2121

2222
## Don't Start from scratch. Reuse an SPFx (web part or extension) or ACE sample
2323

@@ -31,8 +31,8 @@ Switch between the list and grid view and don't worry about the size of your VS
3131

3232
![Sample gallery is responsive](../images/samples-responsive.png)
3333

34-
Check out how easy it is to create a new project based on a existing sample 👇.
34+
Check out how easy it is to create a new project based on an existing sample 👇.
3535

3636
![Create project based on web part sample](../images/sample-gallery.gif)
3737

38-
[Check out our docs for more details](https://github.com/pnp/vscode-viva/wiki/5.2-Scaffolding#2-dont-start-from-scratch---sample-galleries)
38+
[Check out our docs for more details](https://pnp.github.io/vscode-viva/features/scaffolding/#2-dont-start-from-scratch---sample-galleries)

assets/walkthrough/spfx-intro.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,35 @@
11

2-
## SharePoint Framework
2+
# SharePoint Framework
33

44
With SharePoint Framework (SPFx), you can use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready allowing you to create solutions to extend SharePoint, Microsoft Teams, Microsoft Viva Connections, Outlook and Microsoft365.com. This extensibility model allows you to write once and reuse your solutions in multiple Microsoft 365 applications with exactly the same code base.
55

66
The following are some of the key features included as part of the SPFx:
77

8-
- It runs in the context of the current user and connection in the browser. There are no iFrames for the customization (JavaScript is - embedded directly to the page).
8+
- It runs in the context of the current user and connection in the browser. There are no iFrames for the customization (JavaScript is embedded directly into the page).
99
- The controls are rendered in the normal page DOM.
1010
- The controls are responsive and accessible by nature.
1111
- It enables the developer to access the lifecycle in addition to render, load, serialize and deserialize, configuration changes, and more.
1212
- 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.
1313
- The developer toolchain is based on popular open-source client development tools such as NPM, TypeScript, Yeoman, webpack, and gulp.
14-
Performance is reliable.
14+
- Performance is reliable.
1515
- 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.
1616
- SPFx web parts can be added to both classic and modern pages.
1717
- SPFx solutions can be used to extend Microsoft Teams.
1818
- SPFx can be used to extend Microsoft Viva Connections.
19-
- SPFx can be use to extend Outlook and Office 365 app (Office)
19+
- SPFx can be used to extend Outlook and Office 365 app (Office)
2020

2121
With SharePoint Framework you may create client-side web parts, extensions, and adaptive cards.
2222

23-
- Web pats are are controls that appear inside a SharePoint page and execute client-side in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern client-side development tools and the SharePoint workbench (a development test surface). You can deploy your client-side web parts to both modern pages and classic web part pages in Microsoft 365 tenants.
24-
- Extensions allows you to extend the SharePoint user experience. With SPFx Extensions, you can customize more facets of the SharePoint experience, including notification areas, toolbars, list data views, and forms. SPFx Extensions are available in all Microsoft 365 subscriptions for production usage.SPFx Extensions enable you to extend the SharePoint user experience within modern pages and document libraries, while using the familiar SPFx tools and libraries for client-side development. Specifically, the SPFx includes four extension types:
23+
- Web pats are controls that appear inside a SharePoint page and execute client-side in the browser. They're the building blocks of pages that appear on a SharePoint site. You can build client-side web parts using modern client-side development tools and the SharePoint workbench (a development test surface). You can deploy your client-side web parts to both modern pages and classic web part pages in Microsoft 365 tenants.
24+
- Extensions allows you to extend the SharePoint user experience. With SPFx Extensions, you can customize more facets of the SharePoint experience, including notification areas, toolbars, list data views, and forms. SPFx Extensions are available in all Microsoft 365 subscriptions for production usage. SPFx Extensions enable you to extend the SharePoint user experience within modern pages and document libraries, while using the familiar SPFx tools and libraries for client-side development. Specifically, the SPFx includes four extension types:
2525

2626
- Application Customizers: Adds scripts to the page, and accesses well-known HTML element placeholders and extends them with custom renderings.
2727
- Field Customizers: Provides modified views to data for fields within a list.
2828
- Command Sets: Extends the SharePoint command surfaces to add new actions, and provides client-side code that you can use to implement behaviors.
29-
- Form Customizer: Provides a way to assoicate and override default new, edit and view form experience of list and libraries with custom forms by associating component to content type.
29+
- Form Customizer: Provides a way to assoicate and override default new, edit and view form experiences of list and libraries with custom forms by associating component to content type.
3030

31-
- Library components enables you to have independently versioned and deployed code served automatically for the SharePoint Framework components with a deployment through an app catalog. Library components provide you an alternative option to create shared code, which can be then used and referenced cross all the components in the tenant.
32-
- Adaptive Cards Extensions allows you to extend Viva Connections dashboard with your own custom functionalities and visualizations
31+
- Library components enables you to have independently versioned and deployed code served automatically for the SharePoint Framework components with a deployment through an app catalog. Library components provide you an alternative option to create shared code, which can be then used and referenced across all the components in the tenant.
32+
- Adaptive Cards Extensions allow you to extend Viva Connections dashboard with your own custom functionalities and visualizations
3333

3434
Go over the [overview of the SharePoint Framework](https://learn.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview) to find out more.
3535

0 commit comments

Comments
 (0)