Skip to content

Prepare 1.8.0, add CodeQL, and close the canvas mutation survivors - #19

Merged
MPCoreDeveloper merged 1 commit into
mainfrom
chore/1.8.0-release-and-hardening
Nov 14, 2026
Merged

MPCoreDeveloper merged 1 commit into
mainfrom
chore/1.8.0-release-and-hardening

Conversation

@MPCoreDeveloper

Copy link
Copy Markdown
Owner

Summary

Four things, in one change because they meet at the 1.8.0 cut.

1. The 1.8.0 release is prepared

  • <Version>, AssemblyVersion and FileVersion move to 1.8.0; CHANGELOG.md holds ## [1.8.0] - 2026-11-14 and PackageReleaseNotes (which still said 1.6.0) carries the same summary.
  • The public API moves from Unshipped to Shipped: 23 Domain entries (IPdfDiagnoser, PdfDiagnosticsReport, PdfAProfile.PdfA4) and 3 Application entries (PdfDiagnoserService). PublicAPI.Unshipped.txt is back to #nullable enable, and RS0016/RS0017 stay build errors.
  • The manual is rebuilt as the 1.8.0 edition: 27 chapters, 125 pages, 236 bookmarks, check: ok. The preface and the two READMEs say 1.8.0.
  • The tag and the push are the owner's step; docs/release-checklist.md gains the G1–G9 at 1.8.0 section and says which gates are checked (G1–G4, G9) and which are not yet (G6–G8).

2. Two warnings the build had grown are fixed

  • PdfDiagnoserTests passes TestContext.Current.CancellationToken (xUnit1051, 7 warnings).
  • tools/SharpCorePDF.Diagnostics caches one JsonSerializerOptions (CA1869) and accepts --profile 4, which PDF/A-4 made reachable.
  • dotnet build -c Release is 0 warnings, 0 errors again.

3. CodeQL

.github/workflows/codeql.yml runs the C# extractor over the real Release build (both target frameworks), security-extended, on push, pull request and weekly, and uploads SARIF to the Security tab. The actions are pinned by SHA like every other workflow. This is the half of the foundation-readiness “Dependabot or CodeQL” item a file can supply; docs/foundation-readiness.md is refreshed to 2026-11-14 (107 commits, 5 issues, 13 PRs, 9 tags).

4. The canvas mutation survivors are closed

Scoped Stryker run over PdfPageCanvas.cs:

Score Killed Survived Mutants
before 42.04% 66 67 201
after 85.99% 135 13 201

PdfPageCanvasTests adds 33 cases that assert the operations the canvas records rather than the content stream they become: the null/NaN/zero/negative guards, the four cubic curves of an ellipse point by point, and the SaveState/RestoreState counter. docs/mutation-testing.md reads each of the 13 that remain (8 are exception-message strings, 3 are constructor guards default(PdfPageSize) cannot distinguish, 1 is an unreachable ValidatePosition, 1 is the run offset of a left-aligned layout).

Evidence

  • dotnet build .\SharpCorePDF.slnx -c Release → 0 warnings, 0 errors.
  • dotnet test → 1229 passed, 0 failed on net10.0 and on net11.0.
  • dotnet run --project tools\SharpCorePDF.Manual → 27 chapters, 125 pages, 236 bookmarks, check: ok.
  • Stryker 5.1.0, --solution SharpCorePDF.slnx --mutate "**/PdfPageCanvas.cs" → 85.99%.

Note

No src/ production code changed: the canvas hardening is tests only, and the 1.8.0 diff is version metadata plus the API snapshot. The Stryker run over the touched production file is the canvas run above.

The [Unreleased] batch that landed since 1.7.0 is cut as 1.8.0: Version and the assembly and
file versions move to 1.8.0, CHANGELOG holds the entry, PackageReleaseNotes (which still said
1.6.0) carries the same summary, the public API moves from Unshipped to Shipped (23 Domain and
3 Application entries), and the manual is rebuilt as the 1.8.0 edition (27 chapters, 125 pages,
236 bookmarks). The tag and the push are the owner step.

Two warnings the build had grown are fixed: the diagnostics tests pass
TestContext.Current.CancellationToken (xUnit1051, seven warnings) and the diagnostics tool caches
one JsonSerializerOptions (CA1869), so dotnet build -c Release is 0 warnings and 0 errors again.
The tool also accepts --profile 4, which PDF/A-4 made reachable.

CodeQL is added (.github/workflows/codeql.yml): the C# extractor over the real Release build,
security-extended, on push, pull request and weekly, with SARIF in the Security tab. The
foundation-readiness record is refreshed to 2026-11-14 and the release checklist gains the 1.8.0
gate section.

The mutation survivors in PdfPageCanvas.cs are closed: 42.04% to 85.99%, 67 to 13. The new
PdfPageCanvasTests asserts the operations the canvas records - the guards, the four cubic curves
point by point, and the state counter - and docs/mutation-testing.md reads each of the thirteen
that remain. The suite is 1229 on each leg.
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@MPCoreDeveloper
MPCoreDeveloper merged commit a410656 into main Nov 14, 2026
8 checks passed
@MPCoreDeveloper
MPCoreDeveloper deleted the chore/1.8.0-release-and-hardening branch November 14, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants