Thanks for doing this @sat. I’m looking forward to seeing this in action.
I had a quick gander at release_notes.py this morning, and was interested to see that the included commits are initially established based on files changed by the commit intersecting with files that are part of any replica packages (established by bazel). But then this decision is overridden if the file(s) are not considered to be owned by the replica teams. It seems like the important thing should be that a file that constitutes a replica dependency has changed (regardless of who is considered to be the owner of that file). Can I ask what sorts of scenarios this is designed to filter out?
I was also interested to see the EXCLUDE_PACKAGES_FILTERS. Does GuestOS actually take a dependency on ‘/sns/’, ‘/nns/’, ‘ckbtc’, and/or ‘cketh’ files? I’m interested in why these are explicitly filtered out too 