chore(deps): update dependency thisassembly.assemblyinfo to 2.1.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ThisAssembly.AssemblyInfo (source)	2.1.5 → 2.1.6

---

Release Notes

devlooped/ThisAssembly (ThisAssembly.AssemblyInfo)

v2.1.6

Full Changelog

🐛 Fixed bugs:

• Keep the ThisAssembly meta-package private to referencing projects #​518 (@​kzu)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[argus-pr]

✅ Reviewed 22feba3 — nothing to flag.

🤖 @argus-pr — automated AI assistant; replies may be wrong.

[argus-pr]

@argus-pr review — 22feba3 · model deepseek-v4-flash-vision-exp

Summary — This PR bumps the ThisAssembly.AssemblyInfo package version from 2.1.5 to 2.1.6 in Directory.Packages.props, a routine Renovate dependency update. The change is a single-line patch-version bump; the package is consumed with PrivateAssets="all" in src/AsicSharp/AsicSharp.csproj, no lockfile exists to regenerate, and the separate ThisAssembly.Git package is correctly left at 2.1.5.

Risk surface — facts about this change, not findings. A reviewer should start here:

• Dependency changes: dependency manifest(s) changed — verify added/updated dependencies — Directory.Packages.props.

No issues found at or above the MEDIUM threshold. ✅
That is this review finding nothing on the risk surface above — not a finding that there is nothing there.

Severity	Posted	Suppressed
CRITICAL	0	0
HIGH	0	0
MEDIUM	0	0
LOW	0	0

What this review did — 1 of 1 pass(es) over 1 file(s)

• Passes completed: 1 of 1
• Files reviewed: 1 of 1
• Tool calls made while investigating: 5

What it chose to check — the panel's own reading of what mattered here, planned before it looked. Feedback for a reviewer, not a guarantee that each check was completed:

• Read the exact diff of Directory.Packages.props to confirm the change is only the version bump 2.1.5 → 2.1.6 and nothing else was touched (via get_pr_diff on Directory.Packages.props)
• Grep the repo for any other references to ThisAssembly.AssemblyInfo or version 2.1.5 that would need to stay in sync (e.g. other props, csproj, lock files) (via grep for 'ThisAssembly.AssemblyInfo' and '2.1.5' across the repo)
• Confirm the package is actually referenced by a project and that the bump is compatible with the repo's central package management setup (via grep for 'ThisAssembly.AssemblyInfo' in src/**/*.csproj and read Directory.Packages.props context)
• Check whether a packages.lock.json or similar lockfile exists that would need regenerating for the bump to be consistent (via list_dir / grep for 'packages.lock.json')
• Review the release note claim (meta-package private to referencing projects) against how the repo consumes ThisAssembly to see if the patch could change build output (via read the csproj files that reference ThisAssembly.AssemblyInfo and check for any PrivateAssets/ExcludeAssets settings)

---

🤖 Reviewed by @argus-pr (AI, model deepseek-v4-flash-vision-exp) — automated, may be wrong. Reply @argus-pr help for commands.