Measure coverage for pkg folder.

[blkt]

Summary

We recently moved a fair amount of code under from internal to the pkg folder. This fixes our CI configuration to measure coverage for that package as well.

Change Type

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Manually tested.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

Pull Request Test Coverage Report for Build 11600185493

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+2.2%) to 55.214%

---

Files with Coverage Reduction	New Missed Lines	%
internal/authz/authz.go	1	69.85%

Totals
Change from base Build 11590867124:	2.2%
Covered Lines:	15439
Relevant Lines:	27962

---

💛 - Coveralls

[rdimitrov]

@blkt - oh, we might have to pin to certain paths otherwise we reduce the coverage by 14%

Reduces coverage by 14%

[blkt]

@blkt - oh, we might have to pin to certain paths otherwise we reduce the coverage by 14%

Thanks for the ping, I should have fixed that.

By the way, we also have pkg/testkit that is not really a candidate for test coverage. Should we exclude that as well?

[evankanderson]

@blkt - oh, we might have to pin to certain paths otherwise we reduce the coverage by 14%

Thanks for the ping, I should have fixed that.

By the way, we also have pkg/testkit that is not really a candidate for test coverage. Should we exclude that as well?

Probably, at least for now. Depending on how load-bearing that gets, we might want to include it, but let's keep it out for now.