Skip to content

Commit a9fc509

Browse files
HarminderSethiHarminderSethi
authored
Merge branch 'SharePoint:main' into main
2 parents 3e7204a + 7885a79 commit a9fc509

File tree

6 files changed

+63
-8
lines changed

6 files changed

+63
-8
lines changed

‎docs/general-development/site-collection-app-catalog.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Use the site collection app catalog
33
description: Using site collection app catalogs, SharePoint tenant administrators can decentralize the management and scope the deployment of SharePoint add-ins and SharePoint Framework solutions to specific sites.
4-
ms.date: 06/09/2022
4+
ms.date: 05/19/2023
55
ms.assetid: fdf7ecb1-9951-475b-b058-3285fba77b68
66
ms.localizationpriority: high
77
---
@@ -87,7 +87,7 @@ Add-PnPSiteCollectionAppCatalog -site https://contoso.sharepoint.com/sites/marke
8787
Alternatively, use the `spo site appcatalog add` command if you are using the CLI for Microsoft 365:
8888

8989
```console
90-
m365 spo site appcatalog add --url https://contoso.sharepoint.com/sites/marketing
90+
m365 spo site appcatalog add --siteUrl https://contoso.sharepoint.com/sites/marketing
9191
```
9292

9393
After executing this script, the **Apps for SharePoint** library will be added to your site collection where you will be able to deploy SharePoint add-ins and SharePoint Framework solutions.

‎docs/spfx/release-1.17.2.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: SharePoint Framework v1.17.12 release notes
2+
title: SharePoint Framework v1.17.2 release notes
33
description: Release notes for the SharePoint Framework v1.17.2 release
44
ms.date: 05/09/2023
55
ms.localizationpriority: high
@@ -25,7 +25,7 @@ Install the latest release of the SharePoint Framework (SPFx) by including the *
2525
npm install @microsoft/generator-sharepoint@latest --global
2626
```
2727

28-
## Upgrading projects from v1.17 to v1.17.1
28+
## Upgrading projects from v1.17 to v1.17.2
2929

3030
1. In the project's **package.json** file, identify all SPFx v1.17 packages. For each SPFx package:
3131
1. Uninstall the existing v1.17 package:

‎docs/spfx/release-1.17.3.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
title: SharePoint Framework v1.17.3 release notes
3+
description: Release notes for the SharePoint Framework v1.17.3 release
4+
ms.date: 05/09/2023
5+
ms.localizationpriority: high
6+
---
7+
# SharePoint Framework v1.17.3 release notes
8+
9+
This release is a _minor bump_ that fixes the issues around SharePoint Framework solution packaging as listed further down in this document.
10+
11+
We're looking into release more frequent smaller release to be available also in future to address new findings or to address any other known issues, which have been fixed.
12+
13+
> [!TIP]
14+
> It's safe to keep on using SharePoint Framework 1.17 version, but we do recommend using always the latest version in the production, which in this case would be the 1.17.3, which has few minor improvements as listed in this document.
15+
16+
**Released:** May 31, 2023
17+
18+
[!INCLUDE [spfx-release-notes-common](../../includes/snippets/spfx-release-notes-common.md)]
19+
20+
## Install the latest version
21+
22+
Install the latest release of the SharePoint Framework (SPFx) by including the **@latest** tag:
23+
24+
```console
25+
npm install @microsoft/generator-sharepoint@latest --global
26+
```
27+
28+
## Upgrading projects from v1.17 to v1.17.3
29+
30+
1. In the project's **package.json** file, identify all SPFx v1.17 packages. For each SPFx package:
31+
1. Uninstall the existing v1.17 package:
32+
33+
```console
34+
npm uninstall @microsoft/{spfx-package-name}@1.17
35+
```
36+
37+
1. Install the new v1.17.3 package:
38+
39+
```console
40+
npm install @microsoft/{spfx-package-name}@latest --save --save-exact
41+
```
42+
43+
[!INCLUDE [spfx-release-upgrade-tip](../../includes/snippets/spfx-release-upgrade-tip.md)]
44+
45+
## Fixed Issues
46+
47+
Here's a list of specific issues fixed around SharePoint Framework since the previous public release.
48+
49+
- `@fluentui/react` package is referenced both as `dependecy` and `devDependency` in the generated `package.json` file for React Web Part
50+
- [#8966](https://github.com/SharePoint/sp-dev-docs/issues/8966) - Web part missing,Vanishes 1.17/1.17.1/1.17.2
51+
- [#8953](https://github.com/SharePoint/sp-dev-docs/issues/8953) - Lint error occurred with "@typescript-eslint/no-extra-semi"

‎docs/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -466,6 +466,8 @@
466466
items:
467467
- name: Overview
468468
href: spfx/roadmap.md
469+
- name: SPFx v1.17.3 - May 31, 2023
470+
href: spfx/release-1.17.3.md
469471
- name: SPFx v1.17.2 - May 9, 2023
470472
href: spfx/release-1.17.2.md
471473
- name: SPFx v1.17.1 - April 12, 2023

‎docs/transform/modernize-scanner-reports-infopath.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,16 @@
11
---
22
title: The SharePoint modernization scanner reports for the InfoPath scanner mode
33
description: Explains the InfoPath output created by the modernization scanner
4-
ms.date: 10/23/2019
4+
ms.date: 05/30/2023
55
ms.prod: sharepoint
66
ms.localizationpriority: high
77
---
88

99
# SharePoint Modernization scanner reports: InfoPath reports
1010

11+
> [!Note]
12+
> Assessing your InfoPath usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool)
13+
1114
## Excel dashboard
1215

1316
![InfoPath dashboard](media/modernize/excel_infopathusage.png)

‎docs/transform/modernize-scanner.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: The SharePoint modernization scanner
33
description: Gets you started with the SharePoint modernization scanner
4-
ms.date: 06/07/2022
4+
ms.date: 05/30/2023
55
ms.prod: sharepoint
66
ms.localizationpriority: high
77
---
@@ -14,13 +14,12 @@ Using the SharePoint Modernization scanner you can prepare your classic sites fo
1414
- Connecting these sites to a Microsoft 365 group
1515
- Modernizing the wiki and web part pages by creating modern site pages
1616
- Rebuilding classic publishing portals as modern publishing portals
17-
- Understanding where InfoPath is being used
1817
- Understanding the usage of classic blog pages
1918

2019
This scanner is a key tool to use if you want to prepare for modernizing your classic sites as it will give you factual data about how easy it is to modernize your sites. Using the dashboards generated by the scanner you'll be able to drill down on the "modernization readiness" of your sites and plan the needed remediation work where needed.
2120

2221
> [!NOTE]
23-
> - Assessing your workflow 2013 usage should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool), this tool will step by step replace the still relevant features from the modernization scanner
22+
> - Assessing your workflow 2013 and InfoPath Forms Services usages should be done using the [Microsoft 365 Assessment tool](https://aka.ms/microsoft365assessmenttool), this tool will step by step replace the still relevant features from the modernization scanner
2423
> - The SharePoint modernization scanner only is supported for running against SharePoint Online. For scanning on-premises SharePoint you can consider using the [SharePoint Migration Assessment Tool](/sharepointmigration/overview-of-the-sharepoint-migration-assessment-tool) (SMAT) or the [Microsoft Consulting Services open source version of the on-premises workflow scanner](https://github.com/microsoft/SP-Server-Workflow-Scanner).
2524
>
2625
> [!IMPORTANT]

0 commit comments

Comments
 (0)