Bump icalendar from 6.3.2 to 7.2.2

[dependabot]

Bumps icalendar from 6.3.2 to 7.2.2.

Release notes

Sourced from icalendar's releases.

v7.2.2

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.2.1

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.2.0

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.1.3

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.1.2

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.1.1

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.1.0

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.3

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.2

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.1

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.0

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.0a3

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.0a2

To view the changes, please see the Changelog. This release can be installed from PyPI.

v7.0.0a1

To view the changes, please see the Changelog. This release can be installed from PyPI.

Changelog

Sourced from icalendar's changelog.

7.2.2 (2026-07-20)

Documentation

- Fixed duplicate ``vInt.min`` and ``vInt.max`` descriptions in the API reference that caused the Read the Docs build to fail.
7.2.1 (2026-07-20)
Security fixes

• Fixed GHSA-qjcq-q7h7-r74v <https://github.com/collective/icalendar/security/advisories/GHSA-qjcq-q7h7-r74v>_: a crafted REPEAT on a VALARM could exhaust memory or CPU via :attr:Alarm.triggers <icalendar.cal.alarm.Alarm.triggers> and :class:~icalendar.alarms.Alarms. Expansion is now capped at icalendar.config.MAX_ALARM_REPEAT. Its default is 10000. Set to -1 to disable the cap. :class:~icalendar.prop.integer.vInt now also enforces the :rfc:5545 signed 32-bit integer range on parse. @​SashankBhamidi

7.2.0 (2026-06-23)

Removals and deprecations

- Deprecated :func:`icalendar.parser.string.foldline` as a private function for icalendar version 8. @IoannaGiag (`Issue [#1011](https://github.com/collective/icalendar/issues/1011) <https://github.com/collective/icalendar/issues/1011>`_)
- Deprecated :func:`icalendar.parser.string.escape_char`, :func:`icalendar.parser.string.unescape_char`, :func:`icalendar.parser.string.escape_string`, and :func:`icalendar.parser.string.unescape_string` using the standard ``deprecate_for_version_8`` wrapper as per issue [#1405](https://github.com/collective/icalendar/issues/1405). (`Issue [#1405](https://github.com/collective/icalendar/issues/1405) <https://github.com/collective/icalendar/issues/1405>`_)
New features

- Created an :attr:`~icalendar.prop.recur.frequency.vFrequency.ical_value` property for the :class:`~icalendar.prop.recur.frequency.vFrequency` component, mirroring the existing pattern on :class:`~icalendar.prop.recur.weekday.vWeekday`. @mvanhorn (`Issue [#876](https://github.com/collective/icalendar/issues/876) &lt;https://github.com/collective/icalendar/issues/876&gt;`_)
- Created an :attr:`~icalendar.prop.geo.vGeo.ical_value` property for the :class:`~icalendar.prop.geo.vGeo` component. @IoannaGiag (`Issue [#876](https://github.com/collective/icalendar/issues/876) &lt;https://github.com/collective/icalendar/issues/876&gt;`_)
- Added type hints to component methods. @Priyanshu-pulak (`Issue [#938](https://github.com/collective/icalendar/issues/938) &lt;https://github.com/collective/icalendar/issues/938&gt;`_)
- Added test coverage for :func:`icalendar.compatibility.deprecate_for_version_8`. AI disclosure: I used GPT-5 Codex to help draft and refine the test and pull request text. I reviewed the output and validated the change locally. @iccccccccccccc (`Issue [#1407](https://github.com/collective/icalendar/issues/1407) &lt;https://github.com/collective/icalendar/issues/1407&gt;`_)
- The :attr:`Alarm.uid &lt;icalendar.cal.alarm.Alarm.uid&gt;` accessor now falls back to vendor-specific UID properties (the existing ``X-ALARMUID`` and the newly added ``X-EVOLUTION-ALARM-UID``) when no canonical ``UID`` is present, so alarms exported by Evolution/GNOME Calendar expose a usable identifier. ``single_string_property`` now accepts an ordered list of fallback keys so further vendor aliases can be added later. AI disclosure: I used GPT-5 Codex (via the Codex CLI) to draft and refine this change and its tests; I reviewed and validated the output locally. @mvanhorn (`Issue [#1421](https://github.com/collective/icalendar/issues/1421) &lt;https://github.com/collective/icalendar/issues/1421&gt;`_)
- The ``rdates`` and ``exdates`` properties are now writable: assigning a list replaces the ``RDATE``/``EXDATE`` values, ``del`` (or assigning an empty list or ``None``) clears them, and assigning the value the getter returns round-trips. Prepared with the assistance of an AI coding agent (Anthropic's Claude). @gaoflow (`Issue [#1442](https://github.com/collective/icalendar/issues/1442) &lt;https://github.com/collective/icalendar/issues/1442&gt;`_)
Bug fixes

- Strictly validate :class:`~icalendar.prop.dt.datetime.vDatetime` values in :meth:`~icalendar.prop.dt.datetime.vDatetime.from_ical` and reject malformed input. This also improves handling of values with a ``TZID`` prefix, per :rfc:`5545#section-3.3.5`, Form [#3](https://github.com/collective/icalendar/issues/3). @uwezkhan (`Issue [#1361](https://github.com/collective/icalendar/issues/1361) &amp;lt;https://github.com/collective/icalendar/issues/1361&amp;gt;`_)
- Preserve an explicit ``VALUE`` parameter (for example ``RDATE;VALUE=PERIOD`` or ``TRIGGER;VALUE=DATE-TIME``) when converting from jCal. Previously :meth:`Component.from_jcal &amp;lt;icalendar.cal.component.Component.from_jcal&amp;gt;` dropped the value type, which is encoded in the jCal type field rather than as a parameter. Prepared with the assistance of an AI coding agent (Anthropic's Claude Opus 4). @gaoflow @lcampanella98 (`Issue [#1426](https://github.com/collective/icalendar/issues/1426) &amp;lt;https://github.com/collective/icalendar/issues/1426&amp;gt;`_)
- For a newline-free string that the operating system can't use as a file path—for example, one containing an embedded null byte or one that is too long—treat it as calendar data, instead of propagating an :exc:`OSError` from :meth:`Component.from_ical &amp;lt;icalendar.cal.component.Component.from_ical&amp;gt;`. Such input now raises a consistent :exc:`ValueError` across platforms. The string-versus-path boundary is now covered by tests. @uwezkhan (`Issue [#1436](https://github.com/collective/icalendar/issues/1436) &amp;lt;https://github.com/collective/icalendar/issues/1436&amp;gt;`_)
- Accept the ``(dt, None)`` form that ``rdates``/``exdates`` return for a single date when adding ``RDATE`` or ``EXDATE``, so ``event.add(&amp;quot;RDATE&amp;quot;, (dt, None))`` no longer raises :exc:`TypeError` and the value round-trips. Prepared with the assistance of an AI coding agent (Anthropic's Claude Opus 4). @gaoflow @texttheater (`Issue [#1439](https://github.com/collective/icalendar/issues/1439) &amp;lt;https://github.com/collective/icalendar/issues/1439&amp;gt;`_)
- Anchored the value validation regular expressions with ``\Z`` instead of ``$`` in :class:`~icalendar.prop.recur.weekday.vWeekday`, :meth:`vDuration.from_ical &amp;lt;icalendar.prop.dt.duration.vDuration.from_ical&amp;gt;`, :class:`~icalendar.prop.dt.time.vTime` and :class:`~icalendar.prop.dt.utc_offset.vUTCOffset`. ``$`` matches just before a final ``\n``, so a value with a trailing line break was accepted; for ``vWeekday`` the newline survived in the ``str`` value and was re-emitted into RECUR output. @alhudz
- For iCalendar files that have thousands of bare line breaks, reduce the content line parse time by a quadratic order of magnitude when reading a component with :meth:`Component.from_ical &amp;lt;icalendar.cal.component.Component.from_ical&amp;gt;`. @alhudz
- Parse a ``CATEGORIES`` value that contains an unescaped colon correctly. ``TEXT`` values do not escape ``:``, so a category such as ``CATEGORIES:CONFIDENTIAL,http://example.com/tag`` was truncated to a single ``//example.com/tag`` because the value boundary was found with the last colon on the line instead of the first one outside the parameters. @alhudz
- Parse and serialize jCal iteratively so that deeply nested components no longer raise an uncaught :exc:`RecursionError`. :meth:`Component.from_jcal &amp;lt;icalendar.cal.component.Component.from_jcal&amp;gt;` and :meth:`Component.to_jcal &amp;lt;icalendar.cal.component.Component.to_jcal&amp;gt;` now handle arbitrary nesting depth, matching the iterative iCal parser and serializer. @arshsmith
&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt; 
&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;p&gt;... (truncated)&lt;/p&gt;
&lt;/details&gt;
&lt;details&gt;
&lt;summary&gt;Commits&lt;/summary&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/ad87bcf719fde8088a77c724bc2ae8f09545e0e4&quot;&gt;&lt;code&gt;ad87bcf&lt;/code&gt;&lt;/a&gt; version 7.2.2&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/4e135e1d478bf6c3745b0cdc9c33d890950fa3e9&quot;&gt;&lt;code&gt;4e135e1&lt;/code&gt;&lt;/a&gt; Quit talking about yourself, vInt&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/9a2acb40d0befb3d72f6f3582269a6cccb3c23e1&quot;&gt;&lt;code&gt;9a2acb4&lt;/code&gt;&lt;/a&gt; version 7.2.1&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/f83ae7eec025a0f4a19e90e2894e6d1690baedcd&quot;&gt;&lt;code&gt;f83ae7e&lt;/code&gt;&lt;/a&gt; Hush yer mouth, ruff!&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/b7c2224eb5e044c34ab1c19d3e386d56fac62ba1&quot;&gt;&lt;code&gt;b7c2224&lt;/code&gt;&lt;/a&gt; Merge commit from fork&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/535acd56a67df10ce9b11a6893a2ed421e13a9ac&quot;&gt;&lt;code&gt;535acd5&lt;/code&gt;&lt;/a&gt; Apply Steve's doc tweaks to configure.rst&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/6050a575cf296f838378fc8c5f483c4325fd1849&quot;&gt;&lt;code&gt;6050a57&lt;/code&gt;&lt;/a&gt; Add minimal how-to page for icalendar.config&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/c9187d37834ac95b458d23bfc984e06f493963e8&quot;&gt;&lt;code&gt;c9187d3&lt;/code&gt;&lt;/a&gt; Apply Steve's grammar suggestions&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/5347f04ad2cdbc44cb210d2a61cc70a2edecbbc8&quot;&gt;&lt;code&gt;5347f04&lt;/code&gt;&lt;/a&gt; Document vInt.min, vInt.max and ValueError in class docstring&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/collective/icalendar/commit/3fbc807eb940d3f73baa3416e10328628f214111&quot;&gt;&lt;code&gt;3fbc807&lt;/code&gt;&lt;/a&gt; Move clamping into repeat_property; rename vInt constants to min/max&lt;/li&gt;
&lt;li&gt;Additional commits viewable in &lt;a href=&quot;https://github.com/collective/icalendar/compare/v6.3.2...v7.2.2&quot;&gt;compare view&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/details&gt;

&lt;br /&gt;</code></pre>


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=icalendar&package-manager=uv&previous-version=6.3.2&new-version=7.2.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>