chore(deps): Bump the nuget group with 4 updates by dependabot[bot] · Pull Request #84 · ritten-org/Ritten

dependabot · 2026-10-21T09:36:59Z

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1-rc.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)
- Self-diagnostics messages written to the sinks configured by
  SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
  ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  made the server buffer a full copy of the response for each client that did
  not read it until the request completed or timed out. Responses are now
  written in bounded slices so the server's back-pressure applies.
  (#7957)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  on Linux and macOS made the listener allocate and hold a full copy of the
  response for each client that did not read it until the request completed or
  timed out. Responses are now written in bounded slices.
  (#7957)
- Fixed scrape requests that announce a request body holding a thread pool
  thread after their response had been sent on Linux and macOS for as long as
  the client kept trickling in the body. The connection is now closed after
  responding to a request with a body instead of being kept alive.
  (#7962)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1-rc.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)
- Self-diagnostics messages written to the sinks configured by
  SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
  ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  made the server buffer a full copy of the response for each client that did
  not read it until the request completed or timed out. Responses are now
  written in bounded slices so the server's back-pressure applies.
  (#7957)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  on Linux and macOS made the listener allocate and hold a full copy of the
  response for each client that did not read it until the request completed or
  timed out. Responses are now written in bounded slices.
  (#7957)
- Fixed scrape requests that announce a request body holding a thread pool
  thread after their response had been sent on Linux and macOS for as long as
  the client kept trickling in the body. The connection is now closed after
  responding to a request with a body instead of being kept alive.
  (#7962)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.

Commits viewable in compare view.

Updated ritten from 0.10.0 to 0.26.0.

Release notes

Sourced from ritten's releases.

0.26.0

Added

RetireReportsJob removes the reports of subjects that weren't reported on this time. Add it to a workflow and run it after the subject runs, with their subjects in RetireReportsArguments.Reported.
ReportKey and IPublishedReports, for finding a published report again and removing it.

Changed

IForgejoCommentService and IGitHubCommentService take the report's ReportKey, and list and delete through IPublishedReports. IForgejoCommentService is a singleton, and its Unavailable says why it can't comment.

0.25.0

Added

RunOptions.Subject names what a run is for/about. Mostly helpful for report headings and pull request comments, e.g. Subject = "caddy/infrastructure".

0.24.0

Added

JobOption.Set is public, so a host that builds a job's arguments itself can apply what the command line gave.

Changed

An enum option given a value it doesn't take names the ones it does, e.g. '--kind' takes host or docker, not 'nope'.

0.23.0

Changed

Every service is registered once at the start, and runs are scoped. Workflows and jobs no longer register services: the host composes its clients in Program.cs.
Jobs run with a typed arguments model. Job<TArguments> replaces Job<TSettings>; each property reaches steps as a Run parameter of its type.
Project values moved out of client options. DotNetBuildSettings, PackageRepository, ReleaseSettings, DockerImages and TofuModule are arguments now; GitOptions and NuGetOptions keep only what the environment sets.
Clients are scoped to the run. Anything registered as a singleton that depends on one fails Build.
A resource detector reads the application's services, not the run's.
IGit acts on the repository each call names. Every method takes the repository first, and InRepository is gone.
A command with no directory of its own runs in the project root inside a run, and in the process's directory outside one.

Added

WorkflowApplication.Run(workflow, job, arguments, directory, options), for a host that chooses the job and its arguments itself, and WorkflowApplication.Workflows.
JobCommand.Create and a public WorkflowFlags, for a host building its own command line from Ritten's commands.
WorkflowRegistry.Add<T>() builds the workflow from the application's services, so it can take dependencies.
services.AddGit() and services.AddCommandRunner() register the clients with any host's services, such as a background service's. Outside a run nothing is narrated.
The command runner logs what it runs through ILogger: the executable, its directory and its exit code, never its arguments.

Removed

WorkflowSettings, SettingsValidator, JobArgument, JobArguments, WorkflowRunBuilder and WorkflowRun. Use an arguments model, ArgumentsValidator, and WorkflowApplication.Run.

0.22.0

Fixed

check and deploy work on pull requests in CI again. 0.21.0 unconditionally diffed every PR against the branch, which doesn't exist in a standard CI clone. It now fetches the base first if needed.

Added

IGit.FetchMergeBase. Fetches a branch with enough history for ChangedFilesSince to compare against it.

Changed

ReadShippedChanges and ShippedChanges moved to Ritten.NuGet, in the Ritten.Releases and Ritten.Releases.Steps namespaces, beside the release cadence that decides whether they measure anything. The step now reads the cadence from NuGetOptions, so a job using it needs AddNuGet.

0.21.0

Added

OpenTelemetry support. Add a package reference to Ritten.OpenTelemetry, call builder.AddOpenTelemetry(otel => …) and set OTEL_EXPORTER_OTLP_ENDPOINT._
RunContext.Id and RunContext.Url. The GitHub and Forgejo runtimes expose the URL to see the build logs.
More of the file system. Last-write times, moving a directory, listing directories recursively, and IFileSystem.CreateTempDirectory.
IDocker.ComposeConfig and IDocker.Exec.
IGit.Tags, IGit.IsShallow and IGit.TrackedFiles.

Changed

IDocker.Inspect returns null for a container that doesn't exist, rather than throwing.
IFile, IDirectory and IFileSystem have new members.

0.20.1

Fixed

Broken Forgejo link. The runner was reporting the address it connected with, rather than the public instance URL.

0.20.0

Added

WriteAllText and ReadAllTextIfExists on every IFile. Writes are atomic by default.
IFile.MoveTo, GetUnixFileMode and SetUnixFileMode, the primitives the atomic write is built from.

Changed

IFile.OpenWrite truncates. It used to open an existing file without emptying it, so every whole-file writer carried the same SetLength(0) workaround; they all use WriteAllText now.

0.19.0

Added

Ritten.NuGet. The feed client, NugetRead, CheckVersion, NugetAuthenticate, NugetPush, so a host composing its own jobs can check and publish packages without the tool.
A continuous release cadence. release.cadence in ritten.json — curated or continuous. Under continuous every merge that changes what ships is a release, so a pull request that changes it must move the version.

0.18.0

Changed

Empty reports no longer get commented. A run that stops early before any report section no longer gets posted as a comment on the PR.

0.17.0

Added

ISecretProvider, the secrets provider a host registers. Resolve turns a reference into the secret it names.
Ritten.OnePassword. The first provider: AddOnePassword() resolves op://vault/item/field references through the 1Password CLI, authenticated from the environment or a service-account token file.
EnvironmentFile. Reads an env file the way docker compose --env-file does — NAME=value, comments, quotes — and resolves the references in it through the registered provider, so a file on disk holds the names of secrets and never a value.
TofuEnvironment. The environment a root module is applied to: a variable file and env files, produced by a workflow's own step and read by every OpenTofu step after it.

Changed

The OpenTofu client deploys to any environment. Init, Plan and Apply take the TofuEnvironment per call.
TofuPlan produces its TofuPlanResult.

0.16.1

Fixed

Ritten.OpenTofu is no longer missing. Forgot to include the project in ritten.json.

0.16.0

Added

Ritten.OpenTofu. IOpenTofu over the tofu on the path, with TofuInit, TofuFormatCheck, TofuPlan and TofuApply steps.
SectionName.Infrastructure. What a change would do, or did, to the infrastructure.
Docker steps. ComposeCheck, BuildImages and ComposeUp in Ritten.Docker.
IDocker.ComposeValidate. Resolves the compose file without touching anything, and hands back what compose objected to rather than a pass/fail.
The tool registers the Forgejo runtime. ritten on a Forgejo runner now gets the job summary and the pull request comment Ritten.Forgejo already knew how to write.

0.15.0

Added

Forgejo PR comments. Ritten.Forgejo now keeps one comment per workflow on the pull request under review.
Better Forgejo envrionmen support. The runtime now reads the pull request's number and base ref from the run and registers a PullRequest info model.
IGit.ChangedFilesSince. For checking what files have been changed in a given branch.

0.14.0

Added

IDocker can stop and start a compose stack in place. ComposeStop/ComposeStart. Dry runs report the stop and start.

0.13.0

Added

IGit.IsRepository. Whether the directory the client addresses is a working tree or inside one.
Ritten.Forgejo. The Forgejo Actions runtime: detected on FORGEJO_ACTIONS, claiming the GITHUB_* mirrors the runner exports for GitHub-written workflows so it outranks the GitHub runtime where both are registered.
Ritten.Docker. A docker client for workflows: IDocker builds, tags, pushes and logs in, runs a container to completion, and converges or removes a compose stack.

0.12.0

Added

IGit can address a repository other than the workflow's. InRepository(directory) returns a client bound to that working tree, for a job that maintains a checkout beside its own.
IGit commits and pushes. Stage, Commit, Push (with an optional GitCredential, handed to git through a one-shot credential helper in the environment so it never reaches the remote URL or an argument list), AddRemote, CurrentBranch, Upstream and CommitsAhead join the tagging operations. Dry runs report each write instead of making it.

0.11.0

Added

Added shell auto-completion support through the completion command.

Fixed

prepare no longer describes one version twice. A version whose packages had shipped in part was read as one that had never shipped at all, so prepare staged it a second time.
Notes written after a prepare join the entry they belong to. Preparing a version the changelog already has an entry for now adds the unreleased notes to that entry rather than giving the version a second heading.

Commits viewable in compare view.

Updated Verify.XunitV3 from 32.0.1 to 33.3.4.

Release notes

Sourced from Verify.XunitV3's releases.

33.3.4

#1970 DiffEngine 20.8.2

33.3.3

#1965 Better WSL support

33.3.2

#1960 Reduce assembly size

33.3.1

#1953 Update to Argon 0.38.0

33.3.0

#1951 Paged documents: source and derived targets

33.2.0

#1943 Update NUnit to v5
#1947 Show a text diff in the exception message for a text mismatch

33.1.5

#1942 Bump DiffEngine and TUnit packages

33.1.4

#1940 Exclude TUnit CancellationToken parameters from snapshot naming

33.1.3

#1938 Withdraw a raised delete once its file is in use again

33.1.2

#1933 inline switch records fixes
#1934 Bump SponsorCheck to 0.26.0
#1936 Bump DiffEngine to 20.5.0
#1937 Settle by value

33.1.1

#1931 Bump SponsorCheck to 0.25.0

33.1.0

#1910 Allow custom converters to override built-in converters
#1930 Better Dangling snapshots detection

33.0.2

#1919 Update to SponsorCheck 0.24.0

33.0.1

#1918 Bump SponsorCheck to 0.23.0

33.0.0

The most impactful change in this release is the adoption of the Open Source Maintenance Fee.
So a subset of consumers will be required to sponsor the project

33.0.0-beta.11

33.0.0-beta.10

33.0.0-beta.9

33.0.0-beta.8

33.0.0-beta.7

33.0.0-beta.6

33.0.0-beta.5

33.0.0-beta.4

33.0.0-beta.3

33.0.0-beta.1

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

Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1 Bumps OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1 Bumps ritten from 0.10.0 to 0.26.0 Bumps Verify.XunitV3 from 32.0.1 to 33.3.4 --- updated-dependencies: - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: ritten dependency-version: 0.26.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Verify.XunitV3 dependency-version: 33.3.4 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2026-10-21T09:37:24Z

❌ Ritten

✅ Version

Version 0.26.0 is the latest published version; nothing new to release.

All 12 packages agree on 0.26.0.

✅ Metadata

All 12 packages carry everything a feed asks for.

✅ Changelog

New changes accrue under [Unreleased] until a release is prepared.

❌ Build

The solution failed to build.

Compiler output

/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: No license specified. Package 'Verify' requires a SponsorCheck license property. 'Verify' is published in owner mode, so sponsorship is configured once via an MSBuild property (in Directory.Build.props or the consuming project).
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Set ONE of the following properties (in a <PropertyGroup> in Directory.Build.props or the consuming project):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Option — Sponsor on GitHub Sponsors (https://github.com/VerifyTests/Verify/blob/main/docs/maintenance-fee.md):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_GitHubSponsorAccount><your-github-account></Verify_GitHubSponsorAccount>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Option — Sponsor privately (a private or incognito sponsorship is never bundled, so declare an end month alongside the account; at most 12 months out):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipPrivateUntil>yyyy-MM</Verify_SponsorshipPrivateUntil>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Option — Time-bounded license (replace yyyy-MM with the last covered month):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipLicensedUntil>yyyy-MM</Verify_SponsorshipLicensedUntil>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Option — Claim a publisher-defined exemption (use the example under the one that applies):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: - MaintainerConsulting: Organizations that have engaged any of the core maintainers of Verify in consulting work could be exempt from the Maintenance Fee for 6 months from the final date of that work.
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipExemption>MaintainerConsulting</Verify_SponsorshipExemption>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipExemptionUntil>yyyy-MM</Verify_SponsorshipExemptionUntil>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: - OpenSource: Open source projects that do not generate revenue are exempt. Voluntary donations and sponsorships are not revenue.
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipExemption>OpenSource</Verify_SponsorshipExemption>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: - SmallRevenue: Consumers under US$10,000 annual gross revenue are exempt.
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipExemption>SmallRevenue</Verify_SponsorshipExemption>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Option — Mark as ignored (you accept that the build is in breach of the package license):
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: <Verify_SponsorshipLicenseIgnored>true</Verify_SponsorshipLicenseIgnored>
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: Sponsor at https://github.com/VerifyTests/Verify/blob/main/docs/maintenance-fee.md
/home/runner/.nuget/packages/verify/33.3.4/buildTransitive/Verify.targets(172,5): error SC021: See: https://github.com/SimonCropp/SponsorCheck/blob/main/docs/VerifierDiagnosticCodes.md#sc021

View the run logs

dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Oct 21, 2026

Navigation Menu

Repository navigation

chore(deps): Bump the nuget group with 4 updates - #84

chore(deps): Bump the nuget group with 4 updates#84
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-39c829b954

dependabot Bot commented on behalf of github Oct 21, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 21, 2026 •

edited

Loading

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

1.20.1

1.20.1-rc.1

1.20.1-beta.1

1.20.1

1.20.1-rc.1

1.20.1-beta.1

0.26.0

Added

Changed

0.25.0

Added

0.24.0

Added

Changed

0.23.0

Changed

Added

Removed

0.22.0

Fixed

Added

Changed

0.21.0

Added

Changed

0.20.1

Fixed

0.20.0

Added

Changed

0.19.0

Added

0.18.0

Changed

0.17.0

Added

Changed

0.16.1

Fixed

0.16.0

Added

0.15.0

Added

0.14.0

Added

0.13.0

Added

0.12.0

Added

0.11.0

Added

Fixed

33.3.4

33.3.3

33.3.2

33.3.1

33.3.0

33.2.0

33.1.5

33.1.4

33.1.3

33.1.2

33.1.1

33.1.0

33.0.2

33.0.1

33.0.0

33.0.0-beta.11

33.0.0-beta.10

33.0.0-beta.9

33.0.0-beta.8

33.0.0-beta.7

33.0.0-beta.6

33.0.0-beta.5

33.0.0-beta.4

33.0.0-beta.3

33.0.0-beta.1

dependabot Bot commented on behalf of github Oct 21, 2026 •

edited

Loading

github-actions Bot commented Oct 21, 2026 •

edited

Loading