bleedingdeacons / register / 31257413782
50%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 22
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 91.768%. Remained the same
31257413782

push

github

web-flow 
ci: bump actions to v5, probe credentials, map package sources (#19)

Three unrelated robustness fixes to the package-consumption setup.

actions/checkout, actions/setup-dotnet and actions/setup-java move from v4 to v5.
setup-java v4 is end of life, and the other two were being forced onto Node 24
after the Node 20 deprecation. integrity-sharp already runs v5.

Both jobs gain a credentials preflight. A revoked or expired token is still
non-empty, so it probes the feed rather than only checking the variable is set;
without it, expiry surfaces minutes later as a wall of NU1301/403 restore errors
with no indication that a token is the cause. Unexpected status codes warn rather
than fail, so a registry hiccup does not block CI.

nuget.config gains Package Source Mapping. NuGet otherwise queries every source
for every package, so a GitHub Packages auth failure could fail the restore of
unrelated nuget.org packages. Integrity.* is pinned to the private feed and
everything else to nuget.org. Note the mapping is exhaustive: a package matching
no pattern will not be found, so new first-party prefixes must be added to it.

Verified restore resolves under the mapping with the feed pointed at a local
folder holding the released package — Integrity.Client from the mapped source and
the EF Core/Extensions packages from nuget.org — and that
-p:UseLocalIntegritySharp=true still restores, project references being
unaffected by source mapping.

README now documents the token, its scope, and what expiry looks like.

680 of 741 relevant lines covered (91.77%)

5.28 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31257413782.1 22
91.77
GitHub Action Run
Source Files on build 31257413782