April 2025 highlights: Delivered Swift Code Coverage Reporting Enhancement for Bazel Swift rules, with instrumentation to improve coverage accuracy for Swift targets in macOS unit tests. This closes a long-standing gap in the coverage reporting pipeline and strengthens quality gates for macOS builds. Impact: More reliable coverage metrics for Swift code, enabling better risk assessment and release decisions for macOS targets. What changed: Added instrumented file information to swift_binary and swift_compiler_plugin build rules, ensuring Swift sources from these targets are included in coverage manifests when used with macos_unit_test targets. Commit reference: 8be413e0d9f2a0cb36c2dab53056cc5938b8664f ("Add instrumented files info to `swift_binary` and `swift_compiler_plugin`" (#1512)) in bazelbuild/rules_swift.

January 2025 monthly summary for bazelbuild/rules_swift focused on stabilizing the Swift proto workflow under Bazel by ensuring propagation of package_name and copts attributes into the Swift proto compilation. Implemented changes to compile_swift_protos_for_target to include swift_proto_library attrs, improving build correctness and reproducibility. This work reduces misconfigured flags in proto-related Swift targets and strengthens downstream dependencies' reliability. Commit 991d7c650b9b241aef2d452076d5758833e1743f updated the compilation logic and documented behavior. Overall impact: more predictable Swift builds, fewer flaky issues, and better contributor experience.