Right now, if the action is triggered on issue/PR events, it'll get the entire list of milestones and check all of them. It's more efficient to only get the related milestone (the one that was added or removed), and process only that one.
This optimization will mostly help in the case of bulk operations, where multiple instances of the action will be running in parallel.