Repository navigation
chore(deps): Bump ritten and Verify.XunitV3 - #87
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps ritten from 0.10.0 to 0.27.0 Bumps Verify.XunitV3 from 32.0.1 to 33.3.4 --- updated-dependencies: - dependency-name: ritten dependency-version: 0.27.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>
❌ Ritten✅ VersionVersion 0.27.0 is the latest published version; nothing new to release. All 12 packages agree on 0.27.0. ✅ MetadataAll 12 packages carry everything a feed asks for. ✅ ChangelogNew changes accrue under [Unreleased] until a release is prepared. ❌ BuildThe solution failed to build. Compiler output |
Contributor
Author
|
Superseded by #88. |
dependabot
Bot
deleted the
dependabot/nuget/dot-config/nuget-c4fc93a5f8
branch
October 28, 2026 09:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated ritten from 0.10.0 to 0.27.0.
Release notes
Sourced from ritten's releases.
0.27.0
Added
ToolScope.Pathinstalls a tool into a directory of its own.--tool-path: the tool's command at the directory's top, run by its full path from anywhere, shared with neither the user's tools nor a manifest.ToolInstallArgs.Feedasks a feed beside the configured ones (--add-source), for a tool the machine's own sources may not name.0.26.0
Added
RetireReportsJobremoves 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 inRetireReportsArguments.Reported.ReportKeyandIPublishedReports, for finding a published report again and removing it.Changed
IForgejoCommentServiceandIGitHubCommentServicetake the report'sReportKey, and list and delete throughIPublishedReports.IForgejoCommentServiceis a singleton, and itsUnavailablesays why it can't comment.0.25.0
Added
RunOptions.Subjectnames 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.Setis public, so a host that builds a job's arguments itself can apply what the command line gave.Changed
'--kind' takes host or docker, not 'nope'.0.23.0
Changed
Program.cs.Job<TArguments>replacesJob<TSettings>; each property reaches steps as aRunparameter of its type.DotNetBuildSettings,PackageRepository,ReleaseSettings,DockerImagesandTofuModuleare arguments now;GitOptionsandNuGetOptionskeep only what the environment sets.Build.IGitacts on the repository each call names. Every method takes the repository first, andInRepositoryis gone.Added
WorkflowApplication.Run(workflow, job, arguments, directory, options), for a host that chooses the job and its arguments itself, andWorkflowApplication.Workflows.JobCommand.Createand a publicWorkflowFlags, 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()andservices.AddCommandRunner()register the clients with any host's services, such as a background service's. Outside a run nothing is narrated.ILogger: the executable, its directory and its exit code, never its arguments.Removed
WorkflowSettings,SettingsValidator,JobArgument,JobArguments,WorkflowRunBuilderandWorkflowRun. Use an arguments model,ArgumentsValidator, andWorkflowApplication.Run.0.22.0
Fixed
checkanddeploywork 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 forChangedFilesSinceto compare against it.Changed
ReadShippedChangesandShippedChangesmoved toRitten.NuGet, in theRitten.ReleasesandRitten.Releases.Stepsnamespaces, beside the release cadence that decides whether they measure anything. The step now reads the cadence fromNuGetOptions, so a job using it needsAddNuGet.0.21.0
Added
Ritten.OpenTelemetry, callbuilder.AddOpenTelemetry(otel => …)and setOTEL_EXPORTER_OTLP_ENDPOINT._RunContext.IdandRunContext.Url. The GitHub and Forgejo runtimes expose the URL to see the build logs.IFileSystem.CreateTempDirectory.IDocker.ComposeConfigandIDocker.Exec.IGit.Tags,IGit.IsShallowandIGit.TrackedFiles.Changed
IDocker.Inspectreturnsnullfor a container that doesn't exist, rather than throwing.IFile,IDirectoryandIFileSystemhave new members.0.20.1
Fixed
0.20.0
Added
WriteAllTextandReadAllTextIfExistson everyIFile. Writes are atomic by default.IFile.MoveTo,GetUnixFileModeandSetUnixFileMode, the primitives the atomic write is built from.Changed
IFile.OpenWritetruncates. It used to open an existing file without emptying it, so every whole-file writer carried the sameSetLength(0)workaround; they all useWriteAllTextnow.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.release.cadenceinritten.json—curatedorcontinuous. Undercontinuousevery merge that changes what ships is a release, so a pull request that changes it must move the version.0.18.0
Changed
0.17.0
Added
ISecretProvider, the secrets provider a host registers.Resolveturns a reference into the secret it names.Ritten.OnePassword. The first provider:AddOnePassword()resolvesop://vault/item/fieldreferences through the 1Password CLI, authenticated from the environment or a service-account token file.EnvironmentFile. Reads an env file the waydocker compose --env-filedoes —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
Init,PlanandApplytake theTofuEnvironmentper call.TofuPlanproduces itsTofuPlanResult.0.16.1
Fixed
ritten.json.0.16.0
Added
Ritten.OpenTofu.IOpenTofuover thetofuon the path, withTofuInit,TofuFormatCheck,TofuPlanandTofuApplysteps.SectionName.Infrastructure. What a change would do, or did, to the infrastructure.ComposeCheck,BuildImagesandComposeUpinRitten.Docker.IDocker.ComposeValidate. Resolves the compose file without touching anything, and hands back what compose objected to rather than a pass/fail.rittenon a Forgejo runner now gets the job summary and the pull request commentRitten.Forgejoalready knew how to write.0.15.0
Added
Ritten.Forgejonow keeps one comment per workflow on the pull request under review.PullRequestinfo model.IGit.ChangedFilesSince. For checking what files have been changed in a given branch.0.14.0
Added
IDockercan 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 onFORGEJO_ACTIONS, claiming theGITHUB_*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:IDockerbuilds, tags, pushes and logs in, runs a container to completion, and converges or removes a compose stack.0.12.0
Added
IGitcan 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.IGitcommits and pushes.Stage,Commit,Push(with an optionalGitCredential, 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,UpstreamandCommitsAheadjoin the tagging operations. Dry runs report each write instead of making it.0.11.0
Added
completioncommand.Fixed
prepareno longer describes one version twice. A version whose packages had shipped in part was read as one that had never shipped at all, sopreparestaged it a second time.preparejoin 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
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
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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