Repository navigation
fix: restrict unpublished SharePoint Online pages to owners/editors (#3645) #4437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Jan-Kazlouski-elastic
merged 9 commits into
main
from
fix/3645-spo-unpublished-page-acl
Sep 14, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
26cb436
fix: restrict unpublished SPO pages to owners/editors
Jan-Kazlouski-elastic 5cc890f
fix: log when unpublished site page ACL is restricted
Jan-Kazlouski-elastic 752b13b
Update NOTICE.txt
elasticmachine f04825b
chore: tighten comments in unpublished page ACL fix
Jan-Kazlouski-elastic 6af3774
Merge origin/main into fix/3645-spo-unpublished-page-acl
Jan-Kazlouski-elastic 006df4c
Update NOTICE.txt
elasticmachine 90909cd
Merge branch 'main' into fix/3645-spo-unpublished-page-acl
Jan-Kazlouski-elastic 294661d
fix: treat unparsable page minor version as unpublished
Jan-Kazlouski-elastic bfa62ab
chore: tighten unpublished page version comment
Jan-Kazlouski-elastic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why True?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch
I wanted it to be less restrictive initially, but after thinking about it more, changing this to
Falsemakes more sense. If we can't parse the version, we shouldn't assume the page is published. Same as with_grants_access.