Skip to content

Bump the dotnet-dependencies group with 7 updates - #36

Closed
dependabot[bot] wants to merge 120 commits into
mainfrom
dependabot/nuget/dotnet-dependencies-d5456a54fb
Closed

Bump the dotnet-dependencies group with 7 updates#36
dependabot[bot] wants to merge 120 commits into
mainfrom
dependabot/nuget/dotnet-dependencies-d5456a54fb

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 23, 2026

Copy link
Copy Markdown

Updated Microsoft.Bcl.AsyncInterfaces from 10.0.10 to 10.0.11.

Release notes

Sourced from Microsoft.Bcl.AsyncInterfaces's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.DependencyInjection.Abstractions from 9.0.5 to 10.0.11.

Release notes

Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Abstractions from 9.0.5 to 10.0.11.

Release notes

Sourced from Microsoft.Extensions.Logging.Abstractions's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.9.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v18.8.0...v18.9.0

Commits viewable in compare view.

Updated Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400.

Release notes

Sourced from Microsoft.SourceLink.GitHub's releases.

10.0.400

You can build .NET 10.0 from the repository by cloning the release tag v10.0.400 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.303

You can build .NET 10.0 from the repository by cloning the release tag v10.0.303 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.302

You can build .NET 10.0 from the repository by cloning the release tag v10.0.302 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated PdfPig from 0.1.15 to 0.1.16.

Release notes

Sourced from PdfPig's releases.

0.1.16

What's Changed

New Contributors

Full Changelog: UglyToad/PdfPig@v0.1.15...v0.1.16

Commits viewable in compare view.

Updated xunit.runner.visualstudio from 3.1.5 to 4.0.0.

Release notes

Sourced from xunit.runner.visualstudio's releases.

4.0.0

Release notes: https://xunit.net/releases/visualstudio/4.0.0

4.0.0-pre.5

Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.5

4.0.0-pre.4

Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.4

4.0.0-pre.3

Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.3

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

jjopensoftworks-blip and others added 30 commits July 12, 2026 23:50
@jjopensoftworks-blip
Initial commit
7411895
@jjopensoftworks-blip
Add core functionality for Scrubkit: file extraction and redaction
cd3ecc4 
- Implement PlainTextExtractor to handle various plain text formats (.txt, .md, .csv, etc.).
- Create FolderScrubber as the main entry point for scrubbing files in a directory, supporting multiple extractors and redaction.
- Introduce StandardRedactor for pattern-based redaction of sensitive information (emails, phone numbers, etc.).
- Add tests for FolderScrubber and StandardRedactor to ensure functionality and correctness.
- Include README documentation for usage instructions and core features.
- Establish project structure with appropriate .csproj files and package references.
@jjopensoftworks-blip
Add unit tests for extractors and redactors, including image, PDF, an…
ef6e111 
…d office formats
@jjopensoftworks-blip @claude
Add root build infrastructure
f6c6dbe 
Centralized MSBuild config and tooling shared across the solution:

- Directory.Build.props: shared settings (nullable, langversion, analyzers,
  deterministic + SourceLink, Release warnings-as-errors) and package metadata
  (license, repo URL, icon, MinVer tag-driven versioning, snupkg symbols).
- Directory.Packages.props: Central Package Management with transitive pinning.
- global.json: pin the SDK band (rollForward latestMajor).
- .editorconfig: file-scoped namespaces, usings, and formatting rules.
- build/icon.png: 128x128 package icon.
- build/coverage-gate.py: enforces a line-coverage floor in CI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip
Add CI and release workflows, update dependabot configuration, and en…
0adbeb1 
…hance README
@jjopensoftworks-blip
Add support for asynchronous file processing and enhance parallelism …
e1d7bda 
…options
@jjopensoftworks-blip
Add issue templates, contributing guidelines, and changelog for bette…
2b1254a 
…r community engagement
@jjopensoftworks-blip @claude
Add Scrubkit.Playground sample project
3092de2 
Scrubkit.slnx references samples/Scrubkit.Playground, so the project must be
committed or CI's restore fails with MSB3202 (project file not found).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip @claude
Update repository URLs to renamed repo (drop trailing dash)
4275227 
Repo renamed to jjopensoftworks-blip/Scrubkit; update RepositoryUrl,
PackageProjectUrl, PackageReleaseNotes, README badges, changelog, and the
issue-template discussions link accordingly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip @claude
chore: establish build system, packaging, and release automation
5847d05 
chore: establish complete NuGet build and release infrastructure

Add centralized MSBuild configuration (Directory.Build.props, Directory.Packages.props)
with shared settings, analyzers, MinVer versioning, SourceLink, and symbol packages.

Add CI/CD workflows (GitHub Actions), release automation, and Dependabot configuration
for dependency management and automated releases.

Add community templates: issue templates, contributing guidelines, and changelog.

Add Scrubkit.Playground sample project referenced in the solution.

Update repository URLs to reflect renamed repo (jjopensoftworks-blip/Scrubkit).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip @claude
docs: polish docs, wording, and packaging for the v1.0.0 stable release
716eb88 
No code behavior or public-API changes since 0.1.0-preview.1 — this is a
documentation and packaging pass ahead of the first stable release.

- Redesign the NuGet package README and the Scrubkit.Abstractions README for a
  cleaner, better-spaced layout; shorten the quick-start so long lines no longer
  cause a horizontal scrollbar on the package page.
- Rewrite the package description to lead with the problem it solves and refresh
  the search tags (+text-extraction, +office) for discoverability.
- Remove references to add-on packages that aren't shipped yet from the docs and
  XML comments.
- Reword the scrubbing docs and code comments to neutral language and soften
  absolute claims (redactor is best-effort).
- Rewrite CHANGELOG as per-release notes grouped by Features / Bug fixes with
  Stable/Pre-release badges; document 1.0.0 vs the 0.1.0-preview.1 feature set.
- Bump version examples to v1.0.0; gitignore ROADMAP-ARCHIVE.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip @claude
chore: align author metadata, enable package validation, add RAG recipe
4a1a606 
Phase 7 (stable release & discoverability) repo items:

- Align Authors/Company/Copyright to OpenFreeSoftwares so the package author
  matches the nuget.org owner (consistency helps the ID-prefix reservation).
- Enable EnablePackageValidation — cross-framework API compatibility check now;
  set PackageValidationBaselineVersion=1.0.0 after 1.0.0 ships to guard against
  accidental breaking changes in later releases.
- Add a "Prepare a folder for RAG" recipe to the package README.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip @claude
docs: add RAG recipe to project README; record Phase 7 changes in cha…
975768e 
…ngelog

- Add the "Prepare a folder for RAG" recipe to the top-level README (mirrors the
  package README).
- Update the 1.0.0 changelog entry to cover the RAG recipe, the author/company
  alignment to OpenFreeSoftwares, and enabling package validation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jjopensoftworks-blip
version
43b8484
@jjopensoftworks-blip
Docs/v1.0.0 polish (#7)
ef963ab 
<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
Tag v1.0.0 — stable release
a4fed66
@jjopensoftworks-blip
Make redaction opt-in and add CI test reporting
621d60d 
Redaction now defaults to off (opt-in), with tests updated to match. CI
publishes a test-status summary on every run. Minor packaging and workflow tidy-ups.
@jjopensoftworks-blip
Refresh playground and expand test coverage
5ce6b5b 
Make the playground a neutral extraction demo, and add tests for the
redactor seam, extension filtering, record fields, and more formats.
@jjopensoftworks-blip
Make redaction caller-supplied and refresh docs
b481331 
Redaction is opt-in via an IRedactor you provide (no longer applied on its own);
READMEs reflect the extraction focus. Adds edge-case tests, the playground
screenshot, and ignore-file hygiene. Part of the 1.1.0 release.
@jjopensoftworks-blip
Release 1.1.0
0316f82 
Reposition around offline text + metadata extraction and make redaction
opt-in (caller-supplied IRedactor; nothing is redacted unless requested).
Reconcile the docs with the accepted formats and bucket .htm as Text.
Harden the test suite (offline-guarantee, netstandard2.0 runtime, and a
stat-failed guard) and add a landing page, README banner, and social image.
@jjopensoftworks-blip
Release 1.1.0 — offline extraction repositioning, opt-in redaction & …
611e4f2 
…test hardening (#8)

## Summary

1.1.0 repositions Scrubkit around **offline text + metadata extraction**
and makes
**redaction opt-in**. All changes since `v1.0.0`.

## ⚠️ Behavior changes

- **Redaction is opt-in and caller-driven.** The core returns text as
read and redacts
only when the caller supplies an `IRedactor` via `ReadOptions.Redactor`
(or sets a
`Redaction` level). 1.0.0 redacted by default — set a redactor/level
explicitly if you
  relied on that.
- **`.htm` now reports `TypeBucket = "Text"`** (was `"Other"`).
Extraction was already correct.

## 📖 Positioning & docs

- Package `Title`, `Description`, tags, and both READMEs lead with
extraction.
- Reconciled the docs with the accepted formats — added `.htm`, listed
the image EXIF
types (JPG/PNG/TIFF/HEIC/WebP/GIF/BMP), noted RTF/HTML/XML are read as
raw text.
- Refreshed the playground into a neutral extraction demo with an
extraction-view
  screenshot (synthetic data only).

## 🧪 Tests & tooling

- Expanded coverage: opt-in and custom-`IRedactor` paths, extension
filtering, record
fields, and edge cases (empty folders, uncapped limits, corrupt Office
files).
- **Offline-guarantee test** — fails the build if either shipping
assembly references a
  networking assembly.
- **netstandard2.0 runtime test project** — runs the ns2.0 build
(PolySharp polyfills +
`GetValueOrDefault` shim) on the .NET 8 host, so polyfilled paths are
exercised at runtime.
- **`stat-failed` guard test**.
- CI publishes a per-run **test-status summary**.

## 🐛 Bug fixes

- `Buckets.For` now buckets `.htm` as `Text`.

## 🌐 Site & assets

- `docs/` landing page (GitHub Pages ready), README **hero banner**, and
a 1280×640
  **social-preview** image.

## Release mechanics

- Version is tag-driven (MinVer). After merge, pushing tag **`v1.1.0`**
builds package
  `1.1.0` and triggers the OIDC publish workflow.
- Package-validation baseline is `1.0.0` (API surface unchanged; this is
a behavior change).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
Add changelog page and refresh site and package links
3595730
@jjopensoftworks-blip
Add Scrubkit.Email add-on package (.eml extractor)
17668e3
@jjopensoftworks-blip
Keep Scrubkit.Email tests out of the coverage gate
9251f4c
@jjopensoftworks-blip
Document upcoming 1.2.0 (Scrubkit.Email) in the changelog
eceb22a
@jjopensoftworks-blip
Add Scrubkit.OpenDocument add-on package (.odt/.ods/.odp extractor)
63a3e46
@jjopensoftworks-blip
Add Scrubkit.OpenDocument to the 1.2.0 changelog
ed4f072
@jjopensoftworks-blip
Release 1.2.0
c196311
@jjopensoftworks-blip
Showcase the package family on the landing page
2f9d143
@jjopensoftworks-blip
Bump package validation baseline to 1.2.0
56d01cb
jjopensoftworks-blip and others added 22 commits August 1, 2026 04:25
@jjopensoftworks-blip
Fix release-blocking pack failure: Microsoft.Extensions.AI stable GA (#…
0deae86 
…29)

The v1.10.0 tag's release workflow failed at "dotnet pack" (NU5104):
Scrubkit.Extensions.MicrosoftExtensionsAI (and transitively
Scrubkit.Extensions.SemanticKernel, Scrubkit.All) depended on
Microsoft.Extensions.AI(.Abstractions) 9.0.0-preview.9.24525.1, and a
stable release cannot depend on a prerelease package.

Move to the 9.5.0 stable line (the earliest GA release, keeping the
DI.Abstractions/Logging.Abstractions bump minimal: 9.0.0 -> 9.0.5). The
GA API renamed IChatClient.CompleteAsync/CompleteStreamingAsync to
GetResponseAsync/GetStreamingResponseAsync (ChatCompletion ->
ChatResponse, StreamingChatCompletionUpdate -> ChatResponseUpdate) and
dropped the settable ChatMessage.Text in favor of mutating TextContent
items in Contents; RedactingChatClient and its tests are updated
accordingly.

Verified: full solution build, all 484 tests, and
`dotnet pack -c Release` all succeed (previously failed on pack).

<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
docs: fix stale NuGet package count (10 -> 12)
96526be 
Missed counting Scrubkit.Extensions.MicrosoftExtensionsAI and
Scrubkit.Extensions.SemanticKernel, added in 1.10.0.
@jjopensoftworks-blip
Bump package-validation baseline to 1.10.0
6b8bde4 
v1.10.0 is now published on NuGet, so bump the shared baseline and
drop the brand-new-package overrides in
Scrubkit.Extensions.MicrosoftExtensionsAI and
Scrubkit.Extensions.SemanticKernel — both now inherit the shared
1.10.0 baseline like the rest of the family.
@jjopensoftworks-blip
docs: fix stale NuGet package count (10 -> 12) (#30)
2d464de 
Missed counting Scrubkit.Extensions.MicrosoftExtensionsAI and
Scrubkit.Extensions.SemanticKernel, added in 1.10.0.

<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
Merge branch 'main' into chore/baseline-1.10.0
5e16633
@jjopensoftworks-blip
Bump package-validation baseline to 1.10.0 (#31)
7d368b3 
v1.10.0 is now published on NuGet, so bump the shared baseline and drop
the brand-new-package overrides in
Scrubkit.Extensions.MicrosoftExtensionsAI and
Scrubkit.Extensions.SemanticKernel — both now inherit the shared 1.10.0
baseline like the rest of the family.

<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
chore(metadata): configure copyright and author metadata in Directory…
4370ce2 
….Build.props and .editorconfig
@jjopensoftworks-blip
docs: update author and copyright branding in web documentation
c913e7e
@jjopensoftworks-blip
chore(copyright): add Copyright © 2026 jjopensoftworks-blip code head…
469826a 
…er to source files
@jjopensoftworks-blip
test(copyright): add code headers to test files and assertion for ass…
ccad578 
…embly copyright metadata
@jjopensoftworks-blip
Merge branch 'chore/baseline-1.10.0' into main
215ce33
@jjopensoftworks-blip
feat(platform): add net10.0 TFM (LTS) support across all packages and…
d3e7f15 
… test suites
@jjopensoftworks-blip
Merge branch 'feature/net10-tfm-update' into main
71cca2c
@jjopensoftworks-blip
chore(baseline): bump package validation baseline to 1.11.0
9da9318
@jjopensoftworks-blip
Merge branch 'chore/baseline-1.11.0' into main
581768b
@jjopensoftworks-blip
docs: update web documentation pages for v1.11.0, update global.json …
66c608e 
…SDK to 10.0.100, and add post-release housekeeping to CLAUDE.md
@jjopensoftworks-blip
docs: update web documentation pages for v1.11.0, update global.json … (
bedd33c 
#32)

…SDK to 10.0.100, and add post-release housekeeping to CLAUDE.md

<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@jjopensoftworks-blip
feat: initialize documentation site with landing page and versioned c…
e6e560d 
…hangelog
@jjopensoftworks-blip
perf(core): optimize memory allocations and throughput in StandardRed…
31fe702 
…actor and FolderScrubber
@jjopensoftworks-blip
docs: restore full comment for working copy character masking in Stan…
4ab5f36 
…dardRedactor
@jjopensoftworks-blip
perf redactor scrubber allocations (#33)
a96346d 
<!-- Thanks for contributing! Please keep PRs focused. -->

## What & why

Briefly describe the change and the motivation. Link any related issue
(e.g. `Fixes #123`).

## Checklist

- [ ] `dotnet build Scrubkit.slnx -c Release` passes (no warnings —
Release is warnaserror)
- [ ] `dotnet test Scrubkit.slnx -c Release` passes; new code is covered
- [ ] Public API changes are documented with XML doc comments
- [ ] Kept the Abstractions boundary (no heavy deps in
`Scrubkit.Abstractions`)
- [ ] If dependencies changed: updated `Directory.Packages.props` and
committed refreshed
      `packages.lock.json`
- [ ] Updated `CHANGELOG.md` under `[Unreleased]` if user-facing
@dependabot
Bump the dotnet-dependencies group with 7 updates
35a1dfa 
Bumps Microsoft.Bcl.AsyncInterfaces from 10.0.10 to 10.0.11
Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 9.0.5 to 10.0.11
Bumps Microsoft.Extensions.Logging.Abstractions from 9.0.5 to 10.0.11
Bumps Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0
Bumps Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400
Bumps PdfPig from 0.1.15 to 0.1.16
Bumps xunit.runner.visualstudio from 3.1.5 to 4.0.0

---
updated-dependencies:
- dependency-name: Microsoft.Bcl.AsyncInterfaces
  dependency-version: 10.0.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions
  dependency-version: 10.0.11
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.Extensions.Logging.Abstractions
  dependency-version: 10.0.11
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.9.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.SourceLink.GitHub
  dependency-version: 10.0.400
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: PdfPig
  dependency-version: 0.1.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: xunit.runner.visualstudio
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Aug 23, 2026
@dependabot dependabot Bot mentioned this pull request Aug 23, 2026
Closed
@dependabot @github

dependabot Bot commented on behalf of github Aug 24, 2026

Copy link
Copy Markdown
Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/nuget/dotnet-dependencies-d5456a54fb branch August 24, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jjopensoftworks-blip