Skip to content

Comments

Bump Ical.Net from 4.2.0 to 5.2.1#51

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/desktop/PrivStack.Desktop/Ical.Net-5.2.1
Open

Bump Ical.Net from 4.2.0 to 5.2.1#51
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/desktop/PrivStack.Desktop/Ical.Net-5.2.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 20, 2026 •
edited
Loading

Updated Ical.Net from 4.2.0 to 5.2.1.

Release notes

Sourced from Ical.Net's releases.

5.2.1

What's Changed

Full Changelog: ical-org/ical.net@v5.2.0...v5.2.1

5.2.0

Implemented BYDAY with offset and limiting behavior

The following RRULE cases are now implemented

  1. YEARLY + BYMONTH + numeric BYDAY offsets. Pattern: FREQ=YEARLY;BYMONTH=6,9;BYDAY=2MO
  2. YEARLY + numeric BYDAY without BYMONTH. Pattern: FREQ=YEARLY;BYDAY=20MO
  3. YEARLY + BYMONTH + negative numeric BYDAY. Pattern: FREQ=YEARLY;BYMONTH=6,9;BYDAY=-1SU

Changes in Detail

Full Changelog: ical-org/ical.net@v5.1.4...v5.2.0

5.1.4

Fix: Regression introduced in v5.1.3 affecting RRULE:FREQ=YEARLY when negative BYMONTHDAY or BYYEARDAY values are used. In certain combinations the evaluator could normalize negative positions incorrectly and skip valid occurrences (e.g., end‑of‑month or end‑of‑year instances). This has been fixed — please upgrade to v5.1.4.

Example of an affected rule (prior behavior could skip results):

DTSTART:20250101
RRULE:FREQ=YEARLY;BYYEARDAY=-1,1;BYMONTHDAY=-1,1

What's Changed

Full Changelog: ical-org/ical.net@v5.1.3...v5.1.4

5.1.3

What's Changed

  • Fix: Correct handling RRULE:FREQ=YEARLY combined with BYMONTH and BYWEEKNO. The previous implementation could skip occurrences in some scenarios.
  • Fix: Correct handling RRULE:FREQ=YEARLY when BYMONTH ist missing, e.g. RRULE:FREQ=YEARLY;INTERVAL=2;BYDAY=MO,TU. Now takes the month of DTSTART as a limiter. The previous implementation could show occurrences for wrong months.

Full Changelog: ical-org/ical.net@v5.1.2...v5.1.3

5.1.2

Changes

Details

Big Thanks to New Contributors

Full Changelog: ical-org/ical.net@v5.1.1...v5.1.2

5.1.1

What's Changed in release v5.1.1

  • Fix: CalendarEvents with RecurrenceId were not properly evaluated in some scenarios.
  • Feat: RecurringComponents like CalendarEvent support RECURRENCE-ID with optional RANGE parameter for serialization and deserialization.
  • Wiki: Updated articles about recurrence evaluation

Changes in detail

Full Changelog: ical-org/ical.net@v5.1.0...v5.1.1

5.1.0

What's Changed

New Contributors

Full Changelog: ical-org/ical.net@v5.0.0...v5.1.0

5.0.0

What's Changed

New Contributors

Changelog for latest changes: ical-org/ical.net@v5.0.0-pre.43...v5.0.0
Full Changelog for last GA release: ical-org/ical.net@v4.3.1...v5.0.0

5.0.0-pre.43

What's Changed

Thanks to new Contributors

Full Changelog: ical-org/ical.net@v5.0.0-pre.42...v5.0.0-pre.43

5.0.0-pre.42

What's Changed

Full Changelog: ical-org/ical.net@v5.0.0-pre.41...v5.0.0-pre.42

5.0.0-pre.41

What's Changed

Full Changelog: ical-org/ical.net@v5.0.0-pre.40...v5.0.0-pre.41

5.0.0-pre.40

What's Changed

Full Changelog: ical-org/ical.net@v5.0.0-pre.39...v5.0.0-pre.40

5.0.0-pre.39

v5.0.0-pre.39

  • This is the first public pre-release of the next major version of Ical.Net. It's an extensive rewrite of the library, with a focus on performance, correctness and usability. All issues reported in prior versions have been addressed, and the library has been thoroughly tested, also using the libical test suite.
  • We strongly recommend using the pre-release packages, as they are more stable and feature-complete than the v4.x versions.
  • Feedback is highly appreciated.
  • Breaking changes from v4 are currently listed here.

What's Changed in Detail

4.3.1

What's Changed

  • Update Ical.Net.csproj to use NodaTime 3.2.0 instead of 3.1.12. NodaTime v3.2.0 (released yesterday) brings some welcome changes
  • Replace Ical.Net.nuspec with Directory.Build.props
  • Remove unnecessary nuget dependencies, so NodaTime is again the only one

Resolves #​596

Full Changelog: ical-org/ical.net@v4.3.0...v4.3.1

4.3.0

  • Update the repository from fork laget.se/ical net

Apply the following change after the update:

  • Remove net5.0 as target framework from all projects
  • Update nuget-specific settings
    • Update icon.png file used in Ical.Net.nuspec
    • Update package metadata
    • Remove net5.0 package target framework
    • Update README.md to reflect the current project state with ical-org
    • Fix: Update publish.yml to create deterministic builds for packages, update action versions
  • Update GitHub actions to reflect the changed main branch name
  • Update readme.md
  • Update CI workflows publish.yml and tests.yml
    • Changed runs-on to ubuntu-latest.
    • Added fetch-depth: 0 to actions/checkout@​v4 in both workflows.
    • Added Get version tag step in publish.yml.
    • Included -p:nowarn=1591 in Build steps to suppress warnings.
    • Changed Test verbosity to quiet in both workflows.
    • Updated Build and pack for publishing in publish.yml to use VERSION.
    • Updated Store artifacts step in publish.yml for new naming convention.
    • Updated Push package to NuGet step in publish.yml to use VERSION.
  • Update ProdId constant and NodaTime package version
  • Add back assembly signing to projects and include strong name key
  • Update Ical.Net.Tests.csproj and Ical.Net.csproj to include assembly signing by adding SignAssembly and AssemblyOriginatorKeyFile properties.
    • Replace InternalsVisibleTo with AssemblyAttribute including a public key in Ical.Net.csproj.
    • Add IcalNetStrongnameKey.snk for strong name key.
    • Move InternalsVisibleTo from AssemblyInfo.cs to project file
  • Add class RegexDefaults and update all Regex with RegexDefaults.Timeout which is set to 200 milliseconds

This PR closes the following PRs which have previously been merged into laget.se/ical net
Closes #​491
Closes #​443
Closes #​525
Closes #​528
Closes #​571
Closes #​579
Closes #​584
Closes #​595

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)

@dependabot dependabot bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Feb 20, 2026
@dependabot
Bump Ical.Net from 4.2.0 to 5.2.1
0c6498a 
---
updated-dependencies:
- dependency-name: Ical.Net
  dependency-version: 5.2.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/nuget/desktop/PrivStack.Desktop/Ical.Net-5.2.1 branch from fca9f59 to 0c6498a Compare February 21, 2026 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants