Replace CLI upgrade tips with warning on SPFx release pages#10921
Replace CLI upgrade tips with warning on SPFx release pages#10921garrytrinder wants to merge 10 commits into
Conversation
Replace the TIP recommending CLI for Microsoft 365 for upgrades with a WARNING explaining that upgrading from a previous minor version requires changes across package versions, build configuration files, and toolchain settings. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a TIP after the WARNING on each release page showing the exact npx command to run for upgrading to that specific version using CLI for Microsoft 365's spfx project upgrade command. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…warning The snippet now contains a WARNING, so the filename should reflect that. Updated all references across release pages and the template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 90e3802: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Learn Build status updates of commit 90e3802: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
Replace the TIP recommending CLI for Microsoft 365 for upgrades with a WARNING explaining that upgrading from a previous minor version requires changes across package versions, build configuration files, and toolchain settings. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add a TIP after the WARNING on each release page showing the exact npx command to run for upgrading to that specific version using CLI for Microsoft 365's spfx project upgrade command. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…warning The snippet now contains a WARNING, so the filename should reflect that. Updated all references across release pages and the template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…nder-replace-cli-upgrade-tips-with-warning
90e3802 to
1dd128e
Compare
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 1dd128e:
|
Include the existing pnp-o365cli NOTE snippet after the upgrade TIP on each SPFx release page and the template. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit f2ddca8:
|
Update anchor from Azure AD to Entra ID to match the renamed heading in use-aadhttpclient.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
These pages were missing the warning snippet, version-specific TIP, and community disclaimer that were added to all other release pages. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit c9853a9: 💡 Validation status: suggestions
This comment lists only the first 25 files in the pull request. docs/spfx/release-1.22.0.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
|
Set to draft, found some inconsistencies that I need to investigate. |
Summary
Replaces the existing TIP (recommending CLI for Microsoft 365 for upgrades) on all SPFx release notes pages with:
A WARNING explaining that upgrading from a previous minor version requires changes across package versions, build configuration files, and toolchain settings — and that manually updating
package.jsonalone will result in build failures.A version-specific TIP showing the exact
npxcommand to run for upgrading to that release's version usingm365 spfx project upgrade.Changes
includes/snippets/spfx-release-upgrade-tip.md→ renamed tospfx-release-upgrade-warning.mdwith updated WARNING content