chore(deps): update dependency fluentftp to 54.1.2

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
FluentFTP	54.1.1 → 54.1.2

---

Release Notes

robinrodricks/FluentFTP (FluentFTP)

v54.1.2

• Xamarin
  • Improve error handling during FTP connection to fix intermittent hanging on Xamarin
  • Improve LogVersion in Logger for Mono/Xamarin
  • Improve file upload status messages to help debug upload failures
• Optimization
  • Fix memory leak in CancellationTokenSource affecting AsyncFtpClient and GnuTLS
  • Fix multiple memory leaks after extensive testing
• Maintenance
  • Fix C# code generation for FtpProfile.ToCode to generate encoding code correctly
  • Update log4net from 2.0.15 to 3.3.0 in example projects
  • Add .NET 9 and .NET 10 to log version message

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

[claude]

Dependency Update Review

This is a straightforward patch bump of FluentFTP from 54.1.1 → 54.1.2 in Directory.Packages.props.

What's in this release

The 54.1.2 release includes meaningful improvements:

• Memory leak fixes in CancellationTokenSource affecting AsyncFtpClient and GnuTLS — this is the most noteworthy change, as it could impact long-running pipeline processes that use FTP operations
• Xamarin/Mono stability fixes (intermittent connection hanging, better upload status messages)
• Maintenance (log4net update, .NET 9/10 version reporting in logs)

Assessment

The change is correct and minimal — a single line version bump in the central Directory.Packages.props package management file, following the project's centralized versioning pattern.

The memory leak fix makes this a worthwhile update beyond just a routine patch bump. No API changes are expected from a patch release, so no consumer code should need updates.

No issues found. Safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}