Skip to content

Bump SixLabors.ImageSharp from 3.1.7 to 4.0.0#107

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/SixLabors.ImageSharp-4.0.0
Open

Bump SixLabors.ImageSharp from 3.1.7 to 4.0.0#107
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/SixLabors.ImageSharp-4.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 15, 2026

Copy link
Copy Markdown

Updated SixLabors.ImageSharp from 3.1.7 to 4.0.0.

Release notes

Sourced from SixLabors.ImageSharp's releases.

4.0.0

What's Changed

3.1.12

What's Changed

Full Changelog: SixLabors/ImageSharp@v3.1.11...v3.1.12

3.1.11

What's Changed

Full Changelog: SixLabors/ImageSharp@v3.1.10...v3.1.11

3.1.10

What's Changed

Full Changelog: SixLabors/ImageSharp@v3.1.9...v3.1.10

3.1.9

What's Changed

Full Changelog: SixLabors/ImageSharp@v3.1.8...v3.1.9

3.1.8

What's Changed

Full Changelog: SixLabors/ImageSharp@v3.1.7...v3.1.8

Commits viewable in compare view.

Dependabot compatibility score

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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---
updated-dependencies:
- dependency-name: SixLabors.ImageSharp
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 41ad30d296

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread NovinCRM.csproj
<PackageReference Include="RestSharp" Version="114.0.0" />
<PackageReference Include="Sentry.AspNetCore" Version="6.6.0" />
<PackageReference Include="SixLabors.ImageSharp" Version="3.1.7" />
<PackageReference Include="SixLabors.ImageSharp" Version="4.0.0" />

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Wire up the Six Labors license for v4 builds

ImageSharp 4.0.0 enforces a build-time license for direct PackageReferences; without sixlabors.lic, SixLaborsLicenseFile, or SixLaborsLicenseKey, builds fail. I checked the repo for those settings (rg "SixLaborsLicense|sixlabors\.lic|SIXLABORS") and the GitHub Actions build still runs plain dotnet restore/dotnet build --no-restore, so clean CI checkouts will start failing as soon as this package version is restored unless the license is wired through the project/workflows or the upgrade is deferred.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants