Bump AutoMapper from 14.0.0 to 15.1.3 - #887
Conversation
--- updated-dependencies: - dependency-name: AutoMapper dependency-version: 15.1.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
Build + test assessment (po-2023, read-only — verdict merge = ai-01/jsboige)Tested the major bump Build ✅
Tests ✅ (633/642) — 4 fails all in
|
Closing — this bump would silently revert a ratified decision already implemented in codeNot a judgement call on my part: the repo already encodes the answer, with jsboige's decision cited inline.
and
Merging this PR would remove the pin the suppression is predicated on, without removing the suppression. Independently confirmed before closingLicence flip is real (from the packages themselves, not the changelog):
No free patched version exists: The advisory does not reach this codebase. AutoMapper's footprint is one Precedent is consistent: QuestPDF is pinned at Note on the build/test assessment above@PO-2023's work on this PR was useful and partly redirected the cycle — the Durable follow-up (the reason this keeps reappearing)Dependabot will re-open this indefinitely, because nothing tells it 14.0.0 is a deliberate floor. The enforcement gap is a missing Closing as won't-merge (licence policy), not as stale. 🤖 Coordinator ai-01 |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…nce pin (#871, #887) (#902) - Magick.NET-Q16-AnyCPU 14.14.0 -> 14.15.0 (#871 merged): 14.15.0 is the declared first-patched version for 5 advisories (4 medium + 1 low) that accumulated against 14.14.0. Licence unchanged (Apache-2.0). - NEW AutoMapper row documenting the 14.0.0 licence pin. The rationale previously existed only as a comment in the .csproj, which is not where an agent looks before approving a dependency bump — #887 (Dependabot 15.1.3) would have silently reverted the ratified decision jsboige 2026-06-23 and pulled the repo from MIT into RPL-1.5/commercial. - Note that NuGet audit warnings surface on `restore`, not incremental `build` — an incremental build reports 0 while a forced restore reported 28 NU1901/NU1902 lines. This is how the #587 zero-warning invariant went red without any code change (advisory drift against a pinned version). Docs only; 0 code, 0 config, 0 prod CSV. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ive, 2 non-release flags Release-gate audit of every pipeline dependency, triggered by the accidental discovery (#887) that AutoMapper 15.x flips MIT → RPL-1.5/commercial. No full-set audit had been done; prepared ahead of public release v0.9.0 (ai-01 dispatch). Method: dotnet list package --include-transitive + NuGet Registration API for licenseExpression / licenseUrl / requireLicenseAcceptance. Rule: nuspec is truth (divergence → nuspec wins). Verdict: - Shipping pipeline (Argumentum.AssetConverter) — all 24 direct deps + full transitive closure are permissive (MIT / Apache-2.0 / MS-PL / BSD-3). 0 GPL/AGPL/RPL/SSPL/commercial in the release binary. - The 3 license-pinned deps verified against nuspec: AutoMapper 14.0.0 MIT (15.x RPL — pinned), Magick.NET 14.15.0 Apache-2.0, QuestPDF 2022.12.12 MIT (> = commercial — pinned). Match #902. - type="file" licenses resolved manually (ExtendedXmlSerializer/SharpToken MIT, SkiaSharp/System.* MS-.NET MIT) — the SPDX angle-matter flagged in the dispatch. - 2 non-release items flagged for arbitrage: 1. FluentAssertions 8.5.0 (Tests) — commercial Xceed since v8.0 (2025-02); type=file + requireLicenseAcceptance=true. Test-only, does not ship. 2. UglyToad.PdfPig 1.7.0-custom-5 (AssetConverter) — custom build, not on nuget.org, license undeclared. Real PdfPig = Apache-2.0; custom-build provenance needs confirmation. If both flags resolve permissively, the license gate is PASS. This is a result, not a gap. 0 code change, 0 prod CSV, 0 run. Read-only audit; doc-only. Co-Authored-By: Claude-Code <noreply@anthropic.com>
…24 permissive (gate PASS); 1 test-only flag (#905) * docs(licensing): dependency license inventory — pipeline 100% permissive, 2 non-release flags Release-gate audit of every pipeline dependency, triggered by the accidental discovery (#887) that AutoMapper 15.x flips MIT → RPL-1.5/commercial. No full-set audit had been done; prepared ahead of public release v0.9.0 (ai-01 dispatch). Method: dotnet list package --include-transitive + NuGet Registration API for licenseExpression / licenseUrl / requireLicenseAcceptance. Rule: nuspec is truth (divergence → nuspec wins). Verdict: - Shipping pipeline (Argumentum.AssetConverter) — all 24 direct deps + full transitive closure are permissive (MIT / Apache-2.0 / MS-PL / BSD-3). 0 GPL/AGPL/RPL/SSPL/commercial in the release binary. - The 3 license-pinned deps verified against nuspec: AutoMapper 14.0.0 MIT (15.x RPL — pinned), Magick.NET 14.15.0 Apache-2.0, QuestPDF 2022.12.12 MIT (> = commercial — pinned). Match #902. - type="file" licenses resolved manually (ExtendedXmlSerializer/SharpToken MIT, SkiaSharp/System.* MS-.NET MIT) — the SPDX angle-matter flagged in the dispatch. - 2 non-release items flagged for arbitrage: 1. FluentAssertions 8.5.0 (Tests) — commercial Xceed since v8.0 (2025-02); type=file + requireLicenseAcceptance=true. Test-only, does not ship. 2. UglyToad.PdfPig 1.7.0-custom-5 (AssetConverter) — custom build, not on nuget.org, license undeclared. Real PdfPig = Apache-2.0; custom-build provenance needs confirmation. If both flags resolve permissively, the license gate is PASS. This is a result, not a gap. 0 code change, 0 prod CSV, 0 run. Read-only audit; doc-only. Co-Authored-By: Claude-Code <noreply@anthropic.com> * docs(licensing): #905 reconcile verdict — PdfPig resolved via #908, 24/24 permissive, gate PASS Reconciles the §Verdict headline with the §7.2 finding ai-01 flagged: the title said "100% permissive, all 24 direct deps" while §7.2 documented one direct dep (UglyToad.PdfPig 1.7.0-custom-5) with no declared licence. #908 swapped that dep to the official PdfPig 0.1.14 (Apache-2.0, SPDX expression in the nuspec) — so 24/24 direct deps are now genuinely permissive and the headline is honest. Changes: - §Verdict: headline now "24/24 direct deps permissive", PdfPig-custom marked RESOLVED via #908, only FluentAssertions (test-only, non-shipped) remains flagged. Gate = PASS (no caveat). - §1 table: UglyToad.PdfPig row → PdfPig 0.1.14 Apache-2.0 (official, swapped via #908). - §2 VisualTests row: no longer "contrast" — both projects now use the same official PdfPig. - §3 transitive: UglyToad.PdfPig.* → PdfPig.* 0.1.14 Apache-2.0. - §7.2: marked RESOLVED, original finding retained as audit record. - §8 conclusion: 24/24 permissive, gate PASS, FluentAssertions = separate jsboige arbitration. Co-Authored-By: Claude-Code <noreply@anthropic.com> --------- Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
…vendored npm + AutoMapper) (#910) No dependabot.yml existed in the repo; dependabot was running on GitHub UI/auto-detected config and produced ~34 PRs in a single cycle (mostly the same package bumped across many vendored 2sxc module trees — e.g. loader-utils x5, json5 x4, braces x2). This adds an explicit config encoding the policy ai-01 dispatched (`3zhzkb`): 1. nuget (our .NET pipeline) -> group + ignore AutoMapper majors (license barrier) 2. npm vendored DNNPlatform trees -> group + ignore majors (unvalidated in CI) 3. npm our trees (CardPen, pdf-val) -> group + ignore majors Why groups: collapses multiple same-directory bumps into ONE pull request (N-per-dir -> 1-per-dir). Why ignore-major on npm vendored: a major bump edits package.json in a tree that nothing in CI builds or consumes — #901 (webpack-dev-server 5->6 in Bootstrap 4 Instant) is the canonical case ai-01 held for exactly this reason. Patch/minor are lockfile-only no-ops, merged per precedent #120. Why ignore-major on AutoMapper: 14.0.0 is the LAST MIT release; 15.0.0+ flips to RPL-1.5 / commercial (Lucky Penny). Pinned by decision jsboige 2026-06-23 (#588); ignoring the major at the source stops dependabot re-proposing the commercial line (#887). Directories are enumerated exactly because dependabot does NOT glob directories — each block targets one path. The vendored list (26 trees) is generated from `find package-lock.json`, not hand-typed (gen script in scratchpad). OPEN AS A PR — NOT merged. Scope is a deliberate jsboige arbitration (see PR body, option A vs B). Co-authored-by: Your <your.email@example.com> Co-authored-by: Claude-Code <noreply@anthropic.com>
1 participant
Updated AutoMapper from 14.0.0 to 15.1.3.
Release notes
Sourced from AutoMapper's releases.
15.1.3
What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v15.1.0...v15.1.3
15.1.2
What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v16.1.1...v15.1.2
15.1.1
What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v16.1.1...v15.1.1
15.1.0
What's Changed
New Contributors
Full Changelog: LuckyPennySoftware/AutoMapper@v15.0.1...v15.1.0
15.0.1
What's Changed
Full Changelog: LuckyPennySoftware/AutoMapper@v15.0.0...v15.0.1
This release supersedes the 15.0.0 release, reverting behavior and overloads so that the
AddAutoMapperoverloads separate the "scanning for maps" from the "scanning for dependencies". Unfortunately it's not really possible to combine these two together.This also fixes a critical bug in #4545 that does not work with .NET 4.x applications (as intended).
Because of this, the 15.0.0 will be delisted because of the breaking changes there.
15.0.0
Full Changelog: LuckyPennySoftware/AutoMapper@v14.0.0...v15.0.0
To set your license key:
This also introduced a breaking change with
MapperConfigurationrequiring anILoggerFactoryfor logging purposes:Registering AutoMapper with
services.AddAutoMapperwill automatically supply this parameter. Otherwise you'll need to supply the logger factory.You can obtain your license key at AutoMapper.io
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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.