Skip to content

Changelog for 1.2.4 - #19

Merged
arnelirobles merged 1 commit into
mainfrom
release-1.2.4
Aug 19, 2026
Merged

Changelog for 1.2.4#19
arnelirobles merged 1 commit into
mainfrom
release-1.2.4

Conversation

@arnelirobles

@arnelirobles arnelirobles commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Security release. Changelog only; the fix itself is already on main.

What actually ships

I diffed src/ from the 1.2.3 version bump (9a613f0) to main rather than describing what I assumed changed. Ignoring whitespace, three files differ:

src/Mapsicle.AspNetCore/AspNetCoreExtensions.cs                 using order
src/Mapsicle.Caching/CachingExtensions.cs                       using order
src/Mapsicle.EntityFramework/Mapsicle.EntityFramework.csproj    EF Core 8.0.0 -> 8.0.30

The two .cs changes are dotnet format reordering using directives, verified as semantically identical. So this release contains exactly one substantive change.

Why it is worth releasing on its own

Mapsicle.EntityFramework 1.2.3 on NuGet declares Microsoft.EntityFrameworkCore 8.0.0 (confirmed from the published nuspec, not from the csproj). That resolves Microsoft.Extensions.Caching.Memory 8.0.0, GHSA-qj66-m88j-hmgj, high severity. Every install of 1.2.3 and earlier inherits it, and the fix has been sitting merged and unreleased.

Deliberately not bundled with #5 and #2. Those change behaviour: widening conversions that currently return 0 will start returning values. Anyone taking this release for the advisory should not have to take a behaviour change with it.

The changelog records both as known issues present in this release, with the detail that int to int? and int to int are unaffected, since that is what makes the bug easy to miss.

Verification

  • Full suite green on main: 525 tests across 13 projects, 0 failed
  • dotnet list package --vulnerable --include-transitive clean across all 20 projects
  • The publish workflow reads the version from the tag (VERSION="${GITHUB_REF_NAME#v}", applied as /p:Version=) and there is no <Version> in Directory.Build.props to conflict, so v1.2.4 will publish 1.2.4

Note for the record: the only existing tag is v1.1.0 while NuGet is at 1.2.3, because 1.2.3 shipped under the old push-to-main workflow. v1.2.4 will be the first tag that matches a published version.

Summary by CodeRabbit

  • Documentation
    • Added release notes for Mapsicle 1.2.4.
    • Documented a security-related dependency update.
    • Added notes on source formatting, trusted package publishing, and known issues planned for a future release.

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7f386ca4-960e-4e29-bc4c-41677dacd60b

📥 Commits

Reviewing files that changed from the base of the PR and between b7c76d9 and 2ccd3b3.

📒 Files selected for processing (1)
  • CHANGELOG.md

Included review availability: Your plan provides up to 3 included reviews per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The changelog adds Mapsicle 1.2.4 release notes. The notes document the EF Core upgrade, source-formatting changes, NuGet Trusted Publishing through OIDC, and two issues deferred to version 1.3.0.

Changes

Mapsicle 1.2.4 release documentation

Layer / File(s) Summary
1.2.4 release notes
CHANGELOG.md
Adds release notes for the EF Core security upgrade, source formatting, NuGet OIDC publishing, and deferred numeric-conversion and null-reference mapping issues.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2ccd3

This is a documentation-only changelog update, so no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the primary change: adding the changelog for release 1.2.4.
Description check ✅ Passed The description clearly explains the release scope, security rationale, excluded changes, and verification results, although it does not mirror every template heading.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-1.2.4

Comment @coderabbitai help to get the list of available commands.

@arnelirobles
arnelirobles merged commit fcaac08 into main Aug 19, 2026
8 checks passed
@arnelirobles
arnelirobles deleted the release-1.2.4 branch August 19, 2026 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant