Skip to content

chore(deps): Bump the nuget group with 2 updates - #56

Merged
tom-wolfe merged 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-524f6d0628
Aug 27, 2026
Merged

chore(deps): Bump the nuget group with 2 updates#56
tom-wolfe merged 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-524f6d0628

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 26, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

⚠️ 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 ritten from 0.8.0 to 0.10.0.

Release notes

Sourced from ritten's releases.

0.10.0

Added

  • The tool client works the way the SDK does. IDotNet's tool methods are one per dotnet tool verb — ToolInstall, ToolUpdate, ToolUninstall, and InstalledToolVersion for list.
  • The engine reads and writes project files. IProjectFiles and ProjectFile load a ritten.json as a document, set values by key path, and write it back with everything else intact.
  • Ritten.GitHub maintains GitHub Actions workflows. IActionsWorkflows and ActionsWorkflow read a workflow file, find its jobs by what they run, and write a job or a trigger back into it without disturbing a line of the rest.
  • Ritten.DotNet manages the tool manifest. IDotNet gains ToolUpdate and CreateToolManifest, and DotNetProjects reads what a repository holds.
  • Jobs can declare that they run without a project. IJob.RequiresProject is what lets a job create the project file.
  • Workflows can check compatibility. IWorkflow.IsCompatible answers whether a directory looks like its kind, and WorkflowRegistry.IsCompatible asks each in registration order.
  • A file knows its directory, and a directory can place one. IFile.Directory returns the directory a file is in, so anything writing a nested file can create the path first, and IDirectory.RelativePath(file)/RelativePath(directory) write a path the way a project file spells one.

Changed

  • ritten init is now a job instead of a command. It runs like every other job, with --dry-run, --verbose and the rest, and each workflow declares its own. A repository with no ritten.json yet has its workflow detected by what's in it, or --workflow sets one explicitly.
  • Resolving a repository is its own step. WorkflowApplication.SelectWorkflow detects the workflow for a given directory.
  • Workflows can run without a project file. RittenProject.Resolve answers with a synthetic project when nothing has been written yet.
  • Init ensures rather than scaffolds. Every file it touches is loaded as a document, given whatever it's missing, and written back, so a changelog keeps its entries, a ritten.json keeps all its keys, a tool manifest keeps the other tools it pins, and an Actions workflow keeps its other jobs, triggers, and comments.
  • The Actions workflow is named for the project, and found by what it runs. Ritten owns the jobs it wrote, not the file they live in: a renamed workflow file is updated in place rather than duplicated.

0.9.0

Added

  • The report is written to a file. Every run now leaves its report at artifacts/report.md, so the best thing a run produces is no longer readable only on GitHub Actions.
  • ritten init sets a repository up. It writes the four files a repository needs — ritten.json, CHANGELOG.md, the tool manifest, and the GitHub Actions workflow. --check reports what's missing or has drifted, --verbose shows what a drifted file should say, and --force rewrites the files Ritten generates.
  • Jobs declare what they're for. JobKind classifies a job the way StepKind classifies a step — Work, Check, or Deploy.
  • PhysicalFile and PhysicalDirectory are public. IFile and IDirectory were public with no way for anything outside the engine to produce one, so a module holding a real path had nothing to hand back.
  • Steps can reach the repository root. IGit.RepositoryRoot() returns the root of the repository the workflow is running in, which isn't always the project root.

Fixed

  • The pending comment links to the run logs. Just the same as the completed report comment.
  • Output lines up outside a run. A step's body is indented under its heading, which left a command that runs no steps reporting at two different levels for no reason.

Commits viewable in compare view.

Updated YamlDotNet from 16.3.0 to 18.1.0.

Release notes

Sourced from YamlDotNet's releases.

18.1.0

What's Changed

New Contributors

Full Changelog: aaubry/YamlDotNet@v18.0.0...v18.1.0

Breaking

  • Maximum depth of yaml files is now 130 by default. If you need higher you will need to adjust the maximum yaml depth. Going above 130 runs the risk of stack overflow exceptions when any exception happens inside of the deserialization

18.0.0

What's Changed

  • Add a parse method wrapper and caching to fix AoT compilation by @​EdwardCooke in Add a parse method wrapper and caching to fix AoT compilation aaubry/YamlDotNet#1103
    BREAKING CHANGE This is a breaking change in the TypeInspectorSkeleton class and the ITypeInspector interface by adding 2 methods . Quick fix to resolve those breaking changes in your own custom TypeInspector is to return false on the HasParseMethod method and return null or throw an exception on the Parse method.

Full Changelog: aaubry/YamlDotNet@v17.1.0...v18.0.0

17.1.0

What's Changed

  • Security improvements by @​EdwardCooke in Security improvements aaubry/YamlDotNet#1102
    There was a potential breaking change for large yaml files in the MergingParser. You may need to specify the optional parameter for maximum events to be processed. It default to 100k events which is a very large yaml file.

Full Changelog: aaubry/YamlDotNet@v17.0.0...v17.1.0

17.0.0

What's Changed

New Contributors

Full Changelog: aaubry/YamlDotNet@v16.3.0...v17.0.0

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

@dependabot
chore(deps): Bump the nuget group with 2 updates
eb887fd 
Bumps ritten from 0.8.0 to 0.10.0
Bumps YamlDotNet from 16.3.0 to 18.1.0

---
updated-dependencies:
- dependency-name: ritten
  dependency-version: 0.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: YamlDotNet
  dependency-version: 18.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
...

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 26, 2026
@github-actions

github-actions Bot commented Aug 26, 2026 •
edited
Loading

Copy link
Copy Markdown

✅ Ritten

✅ Version

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

All 6 packages agree on 0.10.0.

✅ Metadata

All 6 packages carry everything a feed asks for.

✅ Changelog

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

✅ Tests

All 582 tests passed.

✅ Coverage

  • Line coverage: 86.8%
  • Branch coverage: 83.1%

View the run logs

@tom-wolfe
tom-wolfe merged commit 21b3577 into main Aug 27, 2026
2 checks passed
@tom-wolfe
tom-wolfe deleted the dependabot/nuget/dot-config/nuget-524f6d0628 branch August 27, 2026 17:42
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

@tom-wolfe