Skip to content

Doc updates for Server SDK 4.8 QFE 1#196

Open
magaylor wants to merge 1 commit into
MicrosoftDocs:mainfrom
magaylor:user/magaylor/20260723_Doc_updates_for_4_8_qfe_1
Open

Doc updates for Server SDK 4.8 QFE 1#196
magaylor wants to merge 1 commit into
MicrosoftDocs:mainfrom
magaylor:user/magaylor/20260723_Doc_updates_for_4_8_qfe_1

Conversation

@magaylor

Copy link
Copy Markdown
Contributor

No description provided.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit af0863b:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File Status Preview URL Details
❌Error Details

  • [Error: CannotMergeCommit] Cannot merge commit af0863b2f623daab042faa3d8d44d62cd6052df5 in branch user/magaylor/20260723_Doc_updates_for_4_8_qfe_1 of repository https://github.com/magaylor/PlayReady into branch main (commit 855d6787538612468e021a3739ceae1bb8e68236). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

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.

@magaylor
magaylor force-pushed the user/magaylor/20260723_Doc_updates_for_4_8_qfe_1 branch from af0863b to b34a02e Compare July 24, 2026 00:12
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit b34a02e:

✅ Validation status: passed

File Status Preview URL Details
Docs/Overview/product-versions.md ✅Succeeded
Docs/Overview/what-is-new/what-is-new-4-8.md ✅Succeeded

For more details, please refer to the build report.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

PoliCheck Scan Report

The 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 found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

@mastanki

Copy link
Copy Markdown
Collaborator

Looks good

@mastanki mastanki self-assigned this Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants