Skip to content

Conversation

bryantbiggs
Copy link
Member

Description

  • Correct access policy logic to support not providing a policy to associate

Motivation and Context

Breaking Changes

  • No

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@bryantbiggs bryantbiggs merged commit 39be61d into master Aug 2, 2025
20 checks passed
antonbabenko pushed a commit that referenced this pull request Aug 2, 2025
## [21.0.7](v21.0.6...v21.0.7) (2025-08-02)

### Bug Fixes

* Correct access policy logic to support not providing a policy to associate ([#3464](#3464)) ([39be61d](39be61d))
@antonbabenko
Copy link
Member

This PR is included in version 21.0.7 🎉

@bryantbiggs bryantbiggs deleted the fix/access-entries branch August 2, 2025 13:19
Copy link

github-actions bot commented Sep 2, 2025

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Access Entry Policy Association: A null value cannot be used as the collection in a 'for' expression.
2 participants