<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Nette Releases</title>
	<link>https://nette.org/cs/releases</link>
	<language>en</language>
	<category>blog</category>
	<docs>http://backend.userland.com/rss</docs>
	<image>
		<url>https://files.nette.org/images/og-nette.png?v=1641878944</url>
		<title>Nette Releases</title>
		<link>https://nette.org/cs/releases</link>
	</image>
	<atom:link rel="self" href="https://nette.org/cs/releases/rss" type="application/rss+xml" />

	<item>
		<title>Security v3.2.8</title>
		<link>https://github.com/nette/security/releases/tag/v3.2.8</link>
		<description>
Security: CookieStorage no longer lets the token from the cookie become the identity of the logged-in user unless an authenticator implementing IdentityHandler exchanges it for the real identity in wakeupIdentity(). The storage now hands over a TokenIdentity, and if it reaches User unexchanged, an InvalidStateException tells you to implement the handler. Applications using cookie storage the documented way, with wakeupIdentity() loading the user by the token, need no change.
Permission – isAllowed($role, $resource) without a privilege now respects a deny of a single privilege on a parent resource, even when the resource itself allows some other privilege.
User – when wakeupIdentity() or getGuestIdentity() throws (a database outage, say), the next call tries again instead of working with half-loaded state.
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Security: <strong>CookieStorage</strong> no longer lets the token from the cookie become the identity of the logged-in user unless an authenticator implementing <strong>IdentityHandler</strong> exchanges it for the real identity in <code>wakeupIdentity()</code>. The storage now hands over a <strong>TokenIdentity</strong>, and if it reaches <code>User</code> unexchanged, an <code>InvalidStateException</code> tells you to implement the handler. Applications using cookie storage the documented way, with <code>wakeupIdentity()</code> loading the user by the token, need no change.</li>
<li><strong>Permission</strong> – <code>isAllowed($role, $resource)</code> without a privilege now respects a deny of a single privilege on a parent resource, even when the resource itself allows some other privilege.</li>
<li><strong>User</strong> – when <code>wakeupIdentity()</code> or <code>getGuestIdentity()</code> throws (a database outage, say), the next call tries again instead of working with half-loaded state.</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 18 Nov 2026 23:28:15 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/security/releases/tag/v3.2.8</guid>
	</item>
	<item>
		<title>Latte v3.1.8</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.8</link>
		<description>✨ New Features

Extension::getAttributeContentTypes() – tell Latte that your custom attributes hold JavaScript, CSS or HTML, and it escapes them exactly like onclick, style or srcdoc. Map names or prefixes, such as &apos;x-on:*&apos; =&gt; ContentType::JavaScript for Alpine or &apos;data-tippy-content&apos; =&gt; ContentType::Html for Tippy, and it works in static values, name={$x} and n:attr alike (#426)

💥 Breaking Changes

srcdoc is escaped as the HTML document it is (see Security), so trusted HTML passed as a plain string is now displayed as text. Wrap it in Latte\Runtime\Html or use |noescape; an Html object now keeps its tags. With migration warnings on, Latte reports every value whose output changes (#425)
A null URL attribute is omitted like any other attribute: &lt;a href={$url}&gt; with null renders no href instead of href=&quot;&quot;. Migration warnings report it (#428)
A positional argument after a named one in {include}, {embed}, {extends}, {layout}, {import} and {sandbox} triggers a deprecation, as PHP forbids such a call; it will be an error in the next minor version

🔒 Security

The srcdoc attribute is escaped twice, as the browser decodes it twice, so &lt;iframe srcdoc=&quot;&lt;p&gt;{$x}&lt;/p&gt;&quot;&gt; cannot smuggle in a &lt;script&gt; (#425)
Vue, petite-vue and AngularJS can no longer find a {{ formed by adjacent outputs such as {$a}{$b}, or printed from a variable inside &lt;script type=&quot;text/template&quot;&gt;

🐛 Bug Fixes

Braces in &lt;textarea&gt; and &lt;title&gt; are printed as they are, so a value like {{ }} passes through a form unchanged (#409)
Blocks and includes in XML templates have the XML content type, so included text is converted by XML rules and including XML into XML works; mixing XML and HTML still works with a deprecation (#433)
|number and |bytes with a locale round half up, the same as without one, and are much faster on repeated calls (#427)
Whitespace: the newline after an indented end tag such as   &lt;/ul&gt;{/if} is kept, and the indentation of a line like     {/block}&lt;/p&gt; stays inside the block (#344)
Loading the same template from concurrent Swoole coroutines or fibers works
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Extension::getAttributeContentTypes()</strong> – tell Latte that your custom attributes hold JavaScript, CSS or HTML, and it escapes them exactly like <code>onclick</code>, <code>style</code> or <code>srcdoc</code>. Map names or prefixes, such as <code>'x-on:*' =&gt; ContentType::JavaScript</code> for Alpine or <code>'data-tippy-content' =&gt; ContentType::Html</code> for Tippy, and it works in static values, <code>name={$x}</code> and <code>n:attr</code> alike (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619984090" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/426" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/426/hovercard" href="https://github.com/nette/latte/pull/426">#426</a>)</li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>srcdoc</strong> is escaped as the HTML document it is (see Security), so trusted HTML passed as a plain string is now displayed as text. Wrap it in <code>Latte\Runtime\Html</code> or use <code>|noescape</code>; an <code>Html</code> object now keeps its tags. With migration warnings on, Latte reports every value whose output changes (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619236984" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/425" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/425/hovercard" href="https://github.com/nette/latte/pull/425">#425</a>)</li>
<li>A <code>null</code> URL attribute is omitted like any other attribute: <code>&lt;a href={$url}&gt;</code> with <code>null</code> renders no <code>href</code> instead of <code>href=""</code>. Migration warnings report it (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5683199670" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/428" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/428/hovercard" href="https://github.com/nette/latte/pull/428">#428</a>)</li>
<li>A positional argument after a named one in <code>{include}</code>, <code>{embed}</code>, <code>{extends}</code>, <code>{layout}</code>, <code>{import}</code> and <code>{sandbox}</code> triggers a deprecation, as PHP forbids such a call; it will be an error in the next minor version</li>
</ul>
<h2>🔒 Security</h2>
<ul>
<li>The <code>srcdoc</code> attribute is escaped twice, as the browser decodes it twice, so <code>&lt;iframe srcdoc="&lt;p&gt;{$x}&lt;/p&gt;"&gt;</code> cannot smuggle in a <code>&lt;script&gt;</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619236984" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/425" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/425/hovercard" href="https://github.com/nette/latte/pull/425">#425</a>)</li>
<li>Vue, petite-vue and AngularJS can no longer find a <code>{{</code> formed by adjacent outputs such as <code>{$a}{$b}</code>, or printed from a variable inside <code>&lt;script type="text/template"&gt;</code></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Braces in <code>&lt;textarea&gt;</code> and <code>&lt;title&gt;</code> are printed as they are, so a value like <code>{{ }}</code> passes through a form unchanged (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4017361842" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/409" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/409/hovercard" href="https://github.com/nette/latte/issues/409">#409</a>)</li>
<li>Blocks and includes in XML templates have the XML content type, so included text is converted by XML rules and including XML into XML works; mixing XML and HTML still works with a deprecation (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6096287010" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/433" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/433/hovercard" href="https://github.com/nette/latte/pull/433">#433</a>)</li>
<li><code>|number</code> and <code>|bytes</code> with a locale round half up, the same as without one, and are much faster on repeated calls (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5645022742" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/427" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/427/hovercard" href="https://github.com/nette/latte/pull/427">#427</a>)</li>
<li>Whitespace: the newline after an indented end tag such as <code>  &lt;/ul&gt;{/if}</code> is kept, and the indentation of a line like <code>    {/block}&lt;/p&gt;</code> stays inside the block (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1844750401" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/344" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/344/hovercard" href="https://github.com/nette/latte/issues/344">#344</a>)</li>
<li>Loading the same template from concurrent Swoole coroutines or fibers works</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 17 Nov 2026 17:52:34 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.8</guid>
	</item>
	<item>
		<title>Latte v3.1.9</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.9</link>
		<description>✨ New Features

Extension::getAttributeContentTypes() – tell Latte that your custom attributes hold JavaScript, CSS or HTML, and it escapes them exactly like onclick, style or srcdoc. Map names or prefixes, such as &apos;x-on:*&apos; =&gt; ContentType::JavaScript for Alpine or &apos;data-tippy-content&apos; =&gt; ContentType::Html for Tippy, and it works in static values, name={$x} and n:attr alike (#426)

⚠️ Behavior Changes

srcdoc – trusted HTML passed as a plain string is now displayed as text (see Security). Wrap it in Latte\Runtime\Html or use |noescape; an Html object now keeps its tags. With migration warnings on, Latte reports every value whose output changes (#425)
A null URL attribute is omitted like any other attribute: &lt;a href={$url}&gt; with null renders no href instead of href=&quot;&quot;. Migration warnings report it (#428)
Deprecated: a positional argument after a named one in {include}, {embed}, {extends}, {layout}, {import} and {sandbox}, as PHP forbids such a call; it will be an error in the next minor version

🔒 Security

The srcdoc attribute is escaped twice, as the browser decodes it twice, so &lt;iframe srcdoc=&quot;&lt;p&gt;{$x}&lt;/p&gt;&quot;&gt; cannot smuggle in a &lt;script&gt; (#425)
Vue, petite-vue and AngularJS can no longer find a {{ formed by adjacent outputs such as {$a}{$b}, or printed from a variable inside &lt;script type=&quot;text/template&quot;&gt;

🐛 Bug Fixes

Braces in &lt;textarea&gt; and &lt;title&gt; are printed as they are, so a value like {{ }} passes through a form unchanged (#409)
Blocks and includes in XML templates have the XML content type, so included text is converted by XML rules and including XML into XML works; mixing XML and HTML still works with a deprecation (#433)
|number and |bytes with a locale round a half away from zero, the same as without one, and are much faster on repeated calls (#427)
Whitespace: the newline after an indented end tag such as   &lt;/ul&gt;{/if} is kept, and the indentation of a line like     {/block}&lt;/p&gt; stays inside the block (#344)
Loading the same template from concurrent Swoole coroutines or fibers works (#404)

Thanks to @vrana for the attribute content types and the srcdoc, URL and XML escaping (#425, #426, #428, #433), and to @vosikar and @zipper for #427 and #424.</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Extension::getAttributeContentTypes()</strong> – tell Latte that your custom attributes hold JavaScript, CSS or HTML, and it escapes them exactly like <code>onclick</code>, <code>style</code> or <code>srcdoc</code>. Map names or prefixes, such as <code>'x-on:*' =&gt; ContentType::JavaScript</code> for Alpine or <code>'data-tippy-content' =&gt; ContentType::Html</code> for Tippy, and it works in static values, <code>name={$x}</code> and <code>n:attr</code> alike (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619984090" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/426" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/426/hovercard" href="https://github.com/nette/latte/pull/426">#426</a>)</li>
</ul>
<h2><g-emoji class="g-emoji" alias="warning">⚠️</g-emoji> Behavior Changes</h2>
<ul>
<li><strong>srcdoc</strong> – trusted HTML passed as a plain string is now displayed as text (see Security). Wrap it in <code>Latte\Runtime\Html</code> or use <code>|noescape</code>; an <code>Html</code> object now keeps its tags. With migration warnings on, Latte reports every value whose output changes (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619236984" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/425" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/425/hovercard" href="https://github.com/nette/latte/pull/425">#425</a>)</li>
<li>A <code>null</code> URL attribute is omitted like any other attribute: <code>&lt;a href={$url}&gt;</code> with <code>null</code> renders no <code>href</code> instead of <code>href=""</code>. Migration warnings report it (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5683199670" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/428" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/428/hovercard" href="https://github.com/nette/latte/pull/428">#428</a>)</li>
<li>Deprecated: a positional argument after a named one in <code>{include}</code>, <code>{embed}</code>, <code>{extends}</code>, <code>{layout}</code>, <code>{import}</code> and <code>{sandbox}</code>, as PHP forbids such a call; it will be an error in the next minor version</li>
</ul>
<h2>🔒 Security</h2>
<ul>
<li>The <code>srcdoc</code> attribute is escaped twice, as the browser decodes it twice, so <code>&lt;iframe srcdoc="&lt;p&gt;{$x}&lt;/p&gt;"&gt;</code> cannot smuggle in a <code>&lt;script&gt;</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619236984" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/425" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/425/hovercard" href="https://github.com/nette/latte/pull/425">#425</a>)</li>
<li>Vue, petite-vue and AngularJS can no longer find a <code>{{</code> formed by adjacent outputs such as <code>{$a}{$b}</code>, or printed from a variable inside <code>&lt;script type="text/template"&gt;</code></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Braces in <code>&lt;textarea&gt;</code> and <code>&lt;title&gt;</code> are printed as they are, so a value like <code>{{ }}</code> passes through a form unchanged (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4017361842" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/409" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/409/hovercard" href="https://github.com/nette/latte/issues/409">#409</a>)</li>
<li>Blocks and includes in XML templates have the XML content type, so included text is converted by XML rules and including XML into XML works; mixing XML and HTML still works with a deprecation (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6096287010" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/433" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/433/hovercard" href="https://github.com/nette/latte/pull/433">#433</a>)</li>
<li><code>|number</code> and <code>|bytes</code> with a locale round a half away from zero, the same as without one, and are much faster on repeated calls (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5645022742" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/427" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/427/hovercard" href="https://github.com/nette/latte/pull/427">#427</a>)</li>
<li>Whitespace: the newline after an indented end tag such as <code>  &lt;/ul&gt;{/if}</code> is kept, and the indentation of a line like <code>    {/block}&lt;/p&gt;</code> stays inside the block (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1844750401" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/344" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/344/hovercard" href="https://github.com/nette/latte/issues/344">#344</a>)</li>
<li>Loading the same template from concurrent Swoole coroutines or fibers works (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3465612653" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/404" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/404/hovercard" href="https://github.com/nette/latte/issues/404">#404</a>)</li>
</ul>
<p>Thanks to <a target=_blank rel=noopener class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/vrana/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/vrana">@vrana</a> for the attribute content types and the <code>srcdoc</code>, URL and XML escaping (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619236984" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/425" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/425/hovercard" href="https://github.com/nette/latte/pull/425">#425</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619984090" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/426" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/426/hovercard" href="https://github.com/nette/latte/pull/426">#426</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5683199670" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/428" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/428/hovercard" href="https://github.com/nette/latte/pull/428">#428</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6096287010" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/433" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/433/hovercard" href="https://github.com/nette/latte/pull/433">#433</a>), and to <a target=_blank rel=noopener class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/vosikar/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/vosikar">@vosikar</a> and <a target=_blank rel=noopener class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/zipper/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/zipper">@zipper</a> for <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5645022742" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/427" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/427/hovercard" href="https://github.com/nette/latte/pull/427">#427</a> and <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5387261071" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/424" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/424/hovercard" href="https://github.com/nette/latte/pull/424">#424</a>.</p>
		]]></content:encoded>
		<pubDate>Tue, 17 Nov 2026 17:52:34 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.9</guid>
	</item>
	<item>
		<title>Caching v4.0.0</title>
		<link>https://github.com/nette/caching/releases/tag/v4.0.0</link>
		<description>Two new storages, a lock that really prevents cache stampede, and an API in which a mistake in dependencies or invalidation fails loudly instead of quietly leaving stale data in the cache.
✨ New Features

RedisStorage – a native Redis backend that keeps tags and priorities itself, so it needs no journal, cleans namespaces, and lets only one process generate a missing item while the others wait for it (the lock expires after $lockTimeout)
Psr16Storage – any PSR-16 cache can now serve as a Nette storage; PsrCacheAdapter keeps covering the opposite direction
Dependencies – describe dependencies with a typed object your IDE understands: new Dependencies(expire: &apos;20 minutes&apos;, tags: [...]), or type the generator&apos;s parameter as Dependencies $dp and write $dp-&gt;expire = &apos;20 minutes&apos;; the array with Cache::* keys still works
clean() with named arguments – $cache-&gt;clean(tags: [&quot;article/$id&quot;]), priority: 100 or all: true
Stronger stampede protection – FileStorage reads the item again once it gets the lock, so a process that waited for another one returns the fresh value instead of generating it a second time; a storage opts in through the new LockingReader interface
MemoryStorage honors Expire, Sliding, Tags, Priority and cleaning by namespace, which makes it a realistic stand-in in tests (#85)
SQLiteStorage cleans by namespace and runs in WAL mode, so readers and a writer no longer block each other
serializeData() and unserializeData() of FileStorage can be overridden to store data in another format (#82)
PHPStan now attributes exceptions thrown in the callbacks of load(), bulkLoad() and call() to their caller (#87)

💥 Breaking Changes

Requires PHP 8.4, nette/utils 4.1 and, for the {cache} tag, Latte 3.1
Storage::lock() is gone; a custom storage that should generate a missing item in one process at a time implements LockingReader::readOrGenerate(). Cache::save() with a closure is deprecated, pass the closure to load() as the generator
An unknown key or a value of a wrong type in dependencies or in the conditions of clean() throws an exception, and so does clean() without any condition; expired items are removed by $storage-&gt;clean([])
clean(all: true) on a cache with a namespace removes only that namespace and the ones derived from it; a cache without a namespace still clears the whole storage. Cleaning by Cache::Namespaces includes the derived namespaces as well
A storage throws NotSupportedException for a dependency or condition it cannot honor, such as Priority in SQLiteStorage or cleaning by namespace in MemcachedStorage
PsrCacheAdapter validates keys as PSR-16 requires, so user:1 and other keys with {}()/\@: are rejected
The interfaces IStorage, IJournal and IBulkReader and the service aliases cacheStorage and nette.cacheJournal are removed; the UPPERCASE constants such as Cache::EXPIRE and Cache::start() trigger a deprecation notice

The complete list with migration hints is in docs/upgrading.md.
🐛 Bug Fixes

MemcachedStorage extends a sliding expiration without storing back an item written in between
A failed write to Memcached, such as an item over the size limit, triggers a warning (#71)
FileStorage leaves no empty file behind when a generator fails, and a generator that generates its own item gets an exception instead of waiting for its own lock

⚡ Performance

The FileStorage constructor collects garbage in batches limited to 20 ms instead of walking the whole cache, so a large cache no longer slows down the request that triggers the cleanup
PsrCacheAdapter::getMultiple() reads all the keys in one bulk request
</description>
		<content:encoded><![CDATA[
		<p>Two new storages, a lock that really prevents cache stampede, and an API in which a mistake in dependencies or invalidation fails loudly instead of quietly leaving stale data in the cache.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>RedisStorage</strong> – a native Redis backend that keeps tags and priorities itself, so it needs no journal, cleans namespaces, and lets only one process generate a missing item while the others wait for it (the lock expires after <code>$lockTimeout</code>)</li>
<li><strong>Psr16Storage</strong> – any PSR-16 cache can now serve as a Nette storage; <code>PsrCacheAdapter</code> keeps covering the opposite direction</li>
<li><strong>Dependencies</strong> – describe dependencies with a typed object your IDE understands: <code>new Dependencies(expire: '20 minutes', tags: [...])</code>, or type the generator's parameter as <code>Dependencies $dp</code> and write <code>$dp-&gt;expire = '20 minutes'</code>; the array with <code>Cache::*</code> keys still works</li>
<li><strong>clean() with named arguments</strong> – <code>$cache-&gt;clean(tags: ["article/$id"])</code>, <code>priority: 100</code> or <code>all: true</code></li>
<li><strong>Stronger stampede protection</strong> – FileStorage reads the item again once it gets the lock, so a process that waited for another one returns the fresh value instead of generating it a second time; a storage opts in through the new <code>LockingReader</code> interface</li>
<li><strong>MemoryStorage</strong> honors <code>Expire</code>, <code>Sliding</code>, <code>Tags</code>, <code>Priority</code> and cleaning by namespace, which makes it a realistic stand-in in tests (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3968035367" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/85" data-hovercard-type="pull_request" data-hovercard-url="/nette/caching/pull/85/hovercard" href="https://github.com/nette/caching/pull/85">#85</a>)</li>
<li><strong>SQLiteStorage</strong> cleans by namespace and runs in WAL mode, so readers and a writer no longer block each other</li>
<li><strong>serializeData() and unserializeData()</strong> of FileStorage can be overridden to store data in another format (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2908219227" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/82" data-hovercard-type="issue" data-hovercard-url="/nette/caching/issues/82/hovercard" href="https://github.com/nette/caching/issues/82">#82</a>)</li>
<li>PHPStan now attributes exceptions thrown in the callbacks of <code>load()</code>, <code>bulkLoad()</code> and <code>call()</code> to their caller (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6147386406" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/87" data-hovercard-type="pull_request" data-hovercard-url="/nette/caching/pull/87/hovercard" href="https://github.com/nette/caching/pull/87">#87</a>)</li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li>Requires PHP 8.4, nette/utils 4.1 and, for the <code>{cache}</code> tag, Latte 3.1</li>
<li><code>Storage::lock()</code> is gone; a custom storage that should generate a missing item in one process at a time implements <code>LockingReader::readOrGenerate()</code>. <code>Cache::save()</code> with a closure is deprecated, pass the closure to <code>load()</code> as the generator</li>
<li>An unknown key or a value of a wrong type in dependencies or in the conditions of <code>clean()</code> throws an exception, and so does <code>clean()</code> without any condition; expired items are removed by <code>$storage-&gt;clean([])</code></li>
<li><code>clean(all: true)</code> on a cache with a namespace removes only that namespace and the ones derived from it; a cache without a namespace still clears the whole storage. Cleaning by <code>Cache::Namespaces</code> includes the derived namespaces as well</li>
<li>A storage throws <code>NotSupportedException</code> for a dependency or condition it cannot honor, such as <code>Priority</code> in SQLiteStorage or cleaning by namespace in MemcachedStorage</li>
<li><code>PsrCacheAdapter</code> validates keys as PSR-16 requires, so <code>user:1</code> and other keys with <code>{}()/\@:</code> are rejected</li>
<li>The interfaces <code>IStorage</code>, <code>IJournal</code> and <code>IBulkReader</code> and the service aliases <code>cacheStorage</code> and <code>nette.cacheJournal</code> are removed; the UPPERCASE constants such as <code>Cache::EXPIRE</code> and <code>Cache::start()</code> trigger a deprecation notice</li>
</ul>
<p>The complete list with migration hints is in <code>docs/upgrading.md</code>.</p>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>MemcachedStorage extends a sliding expiration without storing back an item written in between</li>
<li>A failed write to Memcached, such as an item over the size limit, triggers a warning (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1587293638" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/71" data-hovercard-type="issue" data-hovercard-url="/nette/caching/issues/71/hovercard" href="https://github.com/nette/caching/issues/71">#71</a>)</li>
<li>FileStorage leaves no empty file behind when a generator fails, and a generator that generates its own item gets an exception instead of waiting for its own lock</li>
</ul>
<h2>⚡ Performance</h2>
<ul>
<li>The FileStorage constructor collects garbage in batches limited to 20 ms instead of walking the whole cache, so a large cache no longer slows down the request that triggers the cleanup</li>
<li><code>PsrCacheAdapter::getMultiple()</code> reads all the keys in one bulk request</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 06 Nov 2026 17:00:14 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/caching/releases/tag/v4.0.0</guid>
	</item>
	<item>
		<title>Neon v4.0.1</title>
		<link>https://github.com/nette/neon/releases/tag/v4.0.1</link>
		<description>
Inline arrays over several lines read as in JSON – following the NEON specification 1.1, a value on the line after its key belongs to that key, so {a: + new line + b} is {a: b}; the same holds in entity arguments, and a new line may also stand between a key and its colon
Documents written for the old reading change meaning – nette/neon 3 and 4.0.0 read {a: + new line + b} as {a: null, 0: b}. As a transitional aid, parsing a value on the line after its key triggers E_USER_NOTICE naming the line and the key; to keep a key without a value, write null or a comma after it
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Inline arrays over several lines read as in JSON</strong> – following the NEON <a target=_blank rel=noopener href="https://github.com/nette/neon-specification">specification 1.1</a>, a value on the line after its key belongs to that key, so <code>{a:</code> + new line + <code>b}</code> is <code>{a: b}</code>; the same holds in entity arguments, and a new line may also stand between a key and its colon</li>
<li><strong>Documents written for the old reading change meaning</strong> – nette/neon 3 and 4.0.0 read <code>{a:</code> + new line + <code>b}</code> as <code>{a: null, 0: b}</code>. As a transitional aid, parsing a value on the line after its key triggers <code>E_USER_NOTICE</code> naming the line and the key; to keep a key without a value, write <code>null</code> or a comma after it</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 06 Nov 2026 01:28:07 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v4.0.1</guid>
	</item>
	<item>
		<title>Mail v4.2.3</title>
		<link>https://github.com/nette/mail/releases/tag/v4.2.3</link>
		<description>
file configuration key – point it to a directory and every email is saved there as an .eml file instead of being sent, with DKIM signing, redirect and the Tracy panel working just as with a real transport
accessToken configuration key – XOAUTH2 straight from the config; pass a callable such as @App\GoogleOAuth::getAccessToken(...) and an expiring token is fetched fresh for every connection
CssInliner keeps your fallbacks – display: -webkit-box; display: flex survives inlining, within one rule and across rules, so an older email client still finds a value it understands
Message-ID now uses the domain of the sender (Sender or From) instead of the web server&apos;s host or the machine name
SmtpMailer now throws InvalidArgumentException for an unknown encryption (BC break) – a value such as &apos;TLS&apos;, &apos;starttls&apos; or an empty string used to mean an unencrypted connection; use &apos;ssl&apos;, &apos;tls&apos; or null. This also catches a dynamic %env% value the configuration schema cannot check
A persistent SMTP connection silently dropped by a firewall or NAT is now reopened within 5 seconds instead of after the full timeout
Two SMTP edge cases behave sensibly now: timeout: 0 leaves the limits to PHP&apos;s default_socket_timeout, and a rejected EHLO is reported as such, staying retryable in FallbackMailer when the rejection is temporary
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong><code>file</code></strong> configuration key – point it to a directory and every email is saved there as an <code>.eml</code> file instead of being sent, with DKIM signing, <code>redirect</code> and the Tracy panel working just as with a real transport</li>
<li><strong><code>accessToken</code></strong> configuration key – XOAUTH2 straight from the config; pass a callable such as <code>@App\GoogleOAuth::getAccessToken(...)</code> and an expiring token is fetched fresh for every connection</li>
<li><strong>CssInliner</strong> keeps your fallbacks – <code>display: -webkit-box; display: flex</code> survives inlining, within one rule and across rules, so an older email client still finds a value it understands</li>
<li><strong>Message-ID</strong> now uses the domain of the sender (<code>Sender</code> or <code>From</code>) instead of the web server's host or the machine name</li>
<li><strong>SmtpMailer</strong> now throws <code>InvalidArgumentException</code> for an unknown <code>encryption</code> (BC break) – a value such as <code>'TLS'</code>, <code>'starttls'</code> or an empty string used to mean an unencrypted connection; use <code>'ssl'</code>, <code>'tls'</code> or <code>null</code>. This also catches a dynamic <code>%env%</code> value the configuration schema cannot check</li>
<li>A persistent SMTP connection silently dropped by a firewall or NAT is now reopened within 5 seconds instead of after the full timeout</li>
<li>Two SMTP edge cases behave sensibly now: <code>timeout: 0</code> leaves the limits to PHP's <code>default_socket_timeout</code>, and a rejected EHLO is reported as such, staying retryable in FallbackMailer when the rejection is temporary</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 06 Nov 2026 01:27:47 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.2.3</guid>
	</item>
	<item>
		<title>Application v3.3.1</title>
		<link>https://github.com/nette/application/releases/tag/v3.3.1</link>
		<description>✨ New Features

Backed enums in parameters – persistent, action, render and signal parameters can now be typed as a backed enum, e.g. renderDefault(Status $status). The URL carries the case value, link(&apos;this&apos;, [&apos;status&apos; =&gt; Status::Active]) just works, and a value that matches no case is answered with a 404 (nette/nette#1558)
PHP 8.6 – Nette Application now installs and runs on it

⚠️ Deprecations

{control} arguments without a comma – write {control menu, $items} instead of {control menu $items}, just as {form}, {input} and {label} already expect; this script adds the missing commas to your templates
Request constants – Request::FORWARD, RESTORED and VARYING are now Request::Forward, Restored and Varying; the old names keep working

🐛 Bug Fixes

n:nonce – works with base64url nonces, as produced by common CSP middlewares, and with a nonce at the very start of the Content-Security-Policy header
#[Parameter] without a default value – when the request lacks it, a nullable property gets null and an array one [], the same as an action argument; any other is answered with a 404
onShutdown – handlers receive null as the second argument after a successful request, as their type callable(Application, ?Throwable) promises, and a typo in the error presenter name no longer bypasses the error handling of run()
Components without a presenter – createComponent&lt;Name&gt;() factories work on a component that is not attached to a presenter; a presenter is needed only when the factory carries #[Requires]
FileResponse – sends Content-Range only with a partial 206 response, and a 416 response states the file size, as RFC 9110 requires
Tracy routing panel – shows defaults and parameters that are not strings again, each string one only once, and its status colors can be overridden with your own CSS

🛡️ Robustness

Hardening – requests with the reserved FORWARD HTTP method are rejected with a 4xx (thanks to Jakub Richtr), FileResponse strips quotes, backslashes and control characters from the file name in Content-Disposition, and actions that keep calling switch() on each other stop with an exception
Overridden createRequest() or requestToUrl() – the DI container now warns about it in a presenter, since links are generated by LinkGenerator and these methods are never called
Edge cases – #[Requires(methods: ...)] on an action or render method can allow a method outside $allowedMethods, isLinkCurrent() does not throw on a target with #[Requires(forward: true)], links to micro routes inside withModule() can be built, and an ambiguous presenter service ends with InvalidPresenterException instead of refreshing the page over and over
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Backed enums in parameters</strong> – persistent, action, render and signal parameters can now be typed as a backed enum, e.g. <code>renderDefault(Status $status)</code>. The URL carries the case value, <code>link('this', ['status' =&gt; Status::Active])</code> just works, and a value that matches no case is answered with a 404 (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1683363901" data-permission-text="Title is private" data-url="https://github.com/nette/nette/issues/1558" data-hovercard-type="issue" data-hovercard-url="/nette/nette/issues/1558/hovercard" href="https://github.com/nette/nette/issues/1558">nette/nette#1558</a>)</li>
<li><strong>PHP 8.6</strong> – Nette Application now installs and runs on it</li>
</ul>
<h2><g-emoji class="g-emoji" alias="warning">⚠️</g-emoji> Deprecations</h2>
<ul>
<li><strong><code>{control}</code> arguments without a comma</strong> – write <code>{control menu, $items}</code> instead of <code>{control menu $items}</code>, just as <code>{form}</code>, <code>{input}</code> and <code>{label}</code> already expect; <a target=_blank rel=noopener href="https://gist.github.com/dg/ec6ee5335db26443660eb9dd367b1bf6">this script</a> adds the missing commas to your templates</li>
<li><strong><code>Request</code> constants</strong> – <code>Request::FORWARD</code>, <code>RESTORED</code> and <code>VARYING</code> are now <code>Request::Forward</code>, <code>Restored</code> and <code>Varying</code>; the old names keep working</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong><code>n:nonce</code></strong> – works with base64url nonces, as produced by common CSP middlewares, and with a nonce at the very start of the <code>Content-Security-Policy</code> header</li>
<li><strong><code>#[Parameter]</code> without a default value</strong> – when the request lacks it, a nullable property gets <code>null</code> and an array one <code>[]</code>, the same as an action argument; any other is answered with a 404</li>
<li><strong><code>onShutdown</code></strong> – handlers receive <code>null</code> as the second argument after a successful request, as their type <code>callable(Application, ?Throwable)</code> promises, and a typo in the error presenter name no longer bypasses the error handling of <code>run()</code></li>
<li><strong>Components without a presenter</strong> – <code>createComponent&lt;Name&gt;()</code> factories work on a component that is not attached to a presenter; a presenter is needed only when the factory carries <code>#[Requires]</code></li>
<li><strong><code>FileResponse</code></strong> – sends <code>Content-Range</code> only with a partial 206 response, and a 416 response states the file size, as RFC 9110 requires</li>
<li><strong>Tracy routing panel</strong> – shows defaults and parameters that are not strings again, each string one only once, and its status colors can be overridden with your own CSS</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li><strong>Hardening</strong> – requests with the reserved <code>FORWARD</code> HTTP method are rejected with a 4xx (thanks to Jakub Richtr), <code>FileResponse</code> strips quotes, backslashes and control characters from the file name in <code>Content-Disposition</code>, and actions that keep calling <code>switch()</code> on each other stop with an exception</li>
<li><strong>Overridden <code>createRequest()</code> or <code>requestToUrl()</code></strong> – the DI container now warns about it in a presenter, since links are generated by <code>LinkGenerator</code> and these methods are never called</li>
<li><strong>Edge cases</strong> – <code>#[Requires(methods: ...)]</code> on an action or render method can allow a method outside <code>$allowedMethods</code>, <code>isLinkCurrent()</code> does not throw on a target with <code>#[Requires(forward: true)]</code>, links to micro routes inside <code>withModule()</code> can be built, and an ambiguous presenter service ends with <code>InvalidPresenterException</code> instead of refreshing the page over and over</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 05 Nov 2026 23:28:19 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.3.1</guid>
	</item>
	<item>
		<title>Bootstrap v3.2.10</title>
		<link>https://github.com/nette/bootstrap/releases/tag/v3.2.10</link>
		<description>
Container::getParameters() – works in applications without nette/http, where %baseUrl% is an empty string
Configurator – adding, removing or replacing an extension in $defaultExtensions, or changing $autowireExcludedClasses, now rebuilds the container without purging the cache
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Container::getParameters()</strong> – works in applications without nette/http, where <code>%baseUrl%</code> is an empty string</li>
<li><strong>Configurator</strong> – adding, removing or replacing an extension in <code>$defaultExtensions</code>, or changing <code>$autowireExcludedClasses</code>, now rebuilds the container without purging the cache</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 05 Nov 2026 14:29:09 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/bootstrap/releases/tag/v3.2.10</guid>
	</item>
	<item>
		<title>Application v3.2.13</title>
		<link>https://github.com/nette/application/releases/tag/v3.2.13</link>
		<description>
PHP 8.6 – Nette Application now installs and runs on it
Components without a presenter – createComponent&lt;Name&gt;() factories now work on a component that is not attached to a presenter; a presenter is needed only when the factory carries #[Requires]
Requests using the reserved FORWARD HTTP method are now rejected with a 4xx (thanks to Jakub Richtr)
FileResponse strips quotes, backslashes and control characters from the file name in Content-Disposition
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>PHP 8.6</strong> – Nette Application now installs and runs on it</li>
<li><strong>Components without a presenter</strong> – <code>createComponent&lt;Name&gt;()</code> factories now work on a component that is not attached to a presenter; a presenter is needed only when the factory carries <code>#[Requires]</code></li>
<li>Requests using the reserved <code>FORWARD</code> HTTP method are now rejected with a 4xx (thanks to Jakub Richtr)</li>
<li><code>FileResponse</code> strips quotes, backslashes and control characters from the file name in <code>Content-Disposition</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 02 Nov 2026 01:52:42 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.2.13</guid>
	</item>
	<item>
		<title>Forms v3.3.1</title>
		<link>https://github.com/nette/forms/releases/tag/v3.3.1</link>
		<description>✨ New Features

New Form::Enum rule checks that a value is a case of a backed enum, so invalid input is caught by validation, in the browser too, before it reaches your typed DTO: -&gt;addRule($form::Enum, arg: Status::class)
Event handlers resolve both parameters by their type, so function (array $values, Form $form) works in onSuccess, onError, onClick and onValidate (#345)
%value in error messages reads naturally: uploaded file names, the items of a multi-choice selection, and dates in the control&apos;s format, on the server and in netteForms.js alike (#302)
Rules Filled, Blank and Valid work with any Control implementation, so custom controls no longer need to extend BaseControl to use them (#346)
PHPStan accepts validators with narrowed parameter types in addRule() and addCondition(), and extension methods that take arguments (#350, #354)
PHP 8.6 is supported

🗑️ Deprecations

A missing comma before {input} and {label} arguments – write {input name, class: &apos;big&apos;} instead of {input name class: &apos;big&apos;}, just as {form} expects since 3.3.0. This script adds the missing commas to your templates.

🐛 Bug Fixes

Events such as onSuccess can again be fired by calling them as methods (#356)
In Latte, $form points back to the enclosing form after a nested {form} closes
Rule messages and translators may return a Stringable object (#349, #312)
A GET form whose action contains a query parameter without a value (?foo) renders correctly (#348)
netteForms.js validates like the server: lengths count characters, min/max compare numerically, a URL may have a query or fragment without a path, AVIF is a default image type, and the browser&apos;s bad-input check respects the validation scope
Exceeding post_max_size reports its own message, and the Numeric rule has a default message
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>New <strong>Form::Enum</strong> rule checks that a value is a case of a backed enum, so invalid input is caught by validation, in the browser too, before it reaches your typed DTO: <code>-&gt;addRule($form::Enum, arg: Status::class)</code></li>
<li>Event handlers resolve both parameters by their type, so <code>function (array $values, Form $form)</code> works in <code>onSuccess</code>, <code>onError</code>, <code>onClick</code> and <code>onValidate</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3252738735" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/345" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/345/hovercard" href="https://github.com/nette/forms/pull/345">#345</a>)</li>
<li><strong>%value</strong> in error messages reads naturally: uploaded file names, the items of a multi-choice selection, and dates in the control's format, on the server and in netteForms.js alike (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1646252563" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/302" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/302/hovercard" href="https://github.com/nette/forms/issues/302">#302</a>)</li>
<li>Rules <strong>Filled</strong>, <strong>Blank</strong> and <strong>Valid</strong> work with any <code>Control</code> implementation, so custom controls no longer need to extend <code>BaseControl</code> to use them (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3660537160" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/346" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/346/hovercard" href="https://github.com/nette/forms/issues/346">#346</a>)</li>
<li>PHPStan accepts validators with narrowed parameter types in <code>addRule()</code> and <code>addCondition()</code>, and extension methods that take arguments (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4539818765" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/350" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/350/hovercard" href="https://github.com/nette/forms/issues/350">#350</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4869725208" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/354" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/354/hovercard" href="https://github.com/nette/forms/pull/354">#354</a>)</li>
<li><strong>PHP 8.6</strong> is supported</li>
</ul>
<h2>🗑️ Deprecations</h2>
<ul>
<li>A missing comma before <code>{input}</code> and <code>{label}</code> arguments – write <code>{input name, class: 'big'}</code> instead of <code>{input name class: 'big'}</code>, just as <code>{form}</code> expects since 3.3.0. <a target=_blank rel=noopener href="https://gist.github.com/dg/ec6ee5335db26443660eb9dd367b1bf6">This script</a> adds the missing commas to your templates.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Events such as <code>onSuccess</code> can again be fired by calling them as methods (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5699973662" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/356" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/356/hovercard" href="https://github.com/nette/forms/issues/356">#356</a>)</li>
<li>In Latte, <code>$form</code> points back to the enclosing form after a nested <code>{form}</code> closes</li>
<li>Rule messages and translators may return a <code>Stringable</code> object (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3973575164" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/349" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/349/hovercard" href="https://github.com/nette/forms/pull/349">#349</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2021432649" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/312" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/312/hovercard" href="https://github.com/nette/forms/pull/312">#312</a>)</li>
<li>A GET form whose action contains a query parameter without a value (<code>?foo</code>) renders correctly (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3699349899" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/348" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/348/hovercard" href="https://github.com/nette/forms/issues/348">#348</a>)</li>
<li>netteForms.js validates like the server: lengths count characters, min/max compare numerically, a URL may have a query or fragment without a path, AVIF is a default image type, and the browser's bad-input check respects the validation scope</li>
<li>Exceeding <code>post_max_size</code> reports its own message, and the <code>Numeric</code> rule has a default message</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 29 Oct 2026 03:59:34 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/forms/releases/tag/v3.3.1</guid>
	</item>
	<item>
		<title>Forms v3.2.10</title>
		<link>https://github.com/nette/forms/releases/tag/v3.2.10</link>
		<description>✨ New Features

PHP 8.6 is supported
%value in error messages now reads naturally for every control: uploaded file names, the items of a multi-choice selection joined by commas, and dates in the control&apos;s format (#302)
Rules Filled, Blank and Valid work with any Control implementation, so custom controls no longer need to extend BaseControl to use them (#346)

🐛 Bug Fixes

Rule messages and translators may return a Stringable object; validation messages, select optgroups and the prompt now accept it (#349, #312)
Form values map onto int-backed enum properties: numeric strings from text and hidden fields convert to the matching case, and a value with no matching case is passed on unchanged
A GET form whose action contains a query parameter without a value (?foo) renders correctly (#348)
Exceeding post_max_size reports its own message instead of the one for file size
A Form or Container subclass that applies the SmartObject trait again works without a fatal error (nette/utils#338)
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>PHP 8.6</strong> is supported</li>
<li><strong>%value</strong> in error messages now reads naturally for every control: uploaded file names, the items of a multi-choice selection joined by commas, and dates in the control's format (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1646252563" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/302" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/302/hovercard" href="https://github.com/nette/forms/issues/302">#302</a>)</li>
<li>Rules <strong>Filled</strong>, <strong>Blank</strong> and <strong>Valid</strong> work with any <code>Control</code> implementation, so custom controls no longer need to extend <code>BaseControl</code> to use them (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3660537160" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/346" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/346/hovercard" href="https://github.com/nette/forms/issues/346">#346</a>)</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Rule messages and translators may return a <code>Stringable</code> object; validation messages, select optgroups and the prompt now accept it (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3973575164" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/349" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/349/hovercard" href="https://github.com/nette/forms/pull/349">#349</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2021432649" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/312" data-hovercard-type="pull_request" data-hovercard-url="/nette/forms/pull/312/hovercard" href="https://github.com/nette/forms/pull/312">#312</a>)</li>
<li>Form values map onto int-backed enum properties: numeric strings from text and hidden fields convert to the matching case, and a value with no matching case is passed on unchanged</li>
<li>A GET form whose action contains a query parameter without a value (<code>?foo</code>) renders correctly (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3699349899" data-permission-text="Title is private" data-url="https://github.com/nette/forms/issues/348" data-hovercard-type="issue" data-hovercard-url="/nette/forms/issues/348/hovercard" href="https://github.com/nette/forms/issues/348">#348</a>)</li>
<li>Exceeding <code>post_max_size</code> reports its own message instead of the one for file size</li>
<li>A <code>Form</code> or <code>Container</code> subclass that applies the <code>SmartObject</code> trait again works without a fatal error (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4577961186" data-permission-text="Title is private" data-url="https://github.com/nette/utils/issues/338" data-hovercard-type="issue" data-hovercard-url="/nette/utils/issues/338/hovercard" href="https://github.com/nette/utils/issues/338">nette/utils#338</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 29 Oct 2026 03:21:20 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/forms/releases/tag/v3.2.10</guid>
	</item>
	<item>
		<title>Component Model v3.2.1</title>
		<link>https://github.com/nette/component-model/releases/tag/v3.2.1</link>
		<description>
Ready for PHP 8.6 – the supported range is now PHP 8.1 to 8.6
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Ready for <strong>PHP 8.6</strong> – the supported range is now PHP 8.1 to 8.6</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 29 Oct 2026 02:52:05 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/component-model/releases/tag/v3.2.1</guid>
	</item>
	<item>
		<title>Bootstrap v3.3.1</title>
		<link>https://github.com/nette/bootstrap/releases/tag/v3.3.1</link>
		<description>
Ready for PHP 8.6
Works with nette/neon 4.0 as well as 3.4
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Ready for <strong>PHP 8.6</strong></li>
<li>Works with <strong>nette/neon 4.0</strong> as well as 3.4</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 28 Oct 2026 02:45:19 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/bootstrap/releases/tag/v3.3.1</guid>
	</item>
	<item>
		<title>Safe Stream v3.0.5</title>
		<link>https://github.com/nette/safe-stream/releases/tag/v3.0.5</link>
		<description>
Ready for PHP 8.6 – SafeStream now officially supports PHP 8.0 through 8.6
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Ready for <strong>PHP 8.6</strong> – SafeStream now officially supports PHP 8.0 through 8.6</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 28 Oct 2026 00:38:46 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/safe-stream/releases/tag/v3.0.5</guid>
	</item>
	<item>
		<title>Database v3.2.10</title>
		<link>https://github.com/nette/database/releases/tag/v3.2.10</link>
		<description>✨ New Features

Ready for PHP 8.6
insert([]) now inserts a row of database defaults on PostgreSQL, SQLite and MS SQL too, not only on MySQL, so saving an empty form works on every engine

🐛 Bug Fixes

Floats keep their full value, both as bound parameters and inlined in SQL; 1/3 or 1e-11 reach the database exactly as they are in PHP
Selection::insert() with a list of rows returns the number of inserted rows, as documented; code that used the returned ActiveRow now gets an int (#330)
transaction() rethrows the original exception even when the final ROLLBACK fails, e.g. after a deadlock
GroupedSelection::limit() respects the offset when the selection belongs to multiple parent rows, and a Selection over a table without a primary key can be re-queried
Conditions skipped by a short-circuited ?and / ?or no longer leave their parameters behind
A where() identical to an existing JOIN condition is no longer dropped, and binary parameters no longer make distinct conditions collide
Row: isset() and offsetExists() give correct answers, including for falsy values
Reflection is more accurate across drivers: column order of composite foreign keys and indexes (MySQL, PostgreSQL), column defaults (PostgreSQL, #329), primary key and identity columns (MS SQL), tables without an explicit schema (MS SQL), autoincrement detection (SQLite) and table resolution along search_path (PostgreSQL)
MS SQL: identifiers containing [ or ] are escaped correctly, and offset-only or zero-limit queries generate valid SQL
The Tracy panel no longer shows duplicate BlueScreen SQL sections with multiple connections

🛡️ Robustness

Constraint violations on SQL Server, CHECK violations on SQLite and more connection-loss codes on PostgreSQL and MySQL now map to the specific exception classes
Misuse reports a clear exception instead of a PHP error: an unknown PDO driver, page() with less than one item per page, related() on a composite primary key, getInsertId() on a failed lazy connection, an unknown table in Reflection on SQLite, an unknown constant in the DI options; the ambiguous-reference message names the table, key and candidates
The DI extension detects a single connection by the presence of dsn, so key order in the config no longer matters
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>Ready for <strong>PHP 8.6</strong></li>
<li><strong>insert([])</strong> now inserts a row of database defaults on PostgreSQL, SQLite and MS SQL too, not only on MySQL, so saving an empty form works on every engine</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Floats keep their full value, both as bound parameters and inlined in SQL; <code>1/3</code> or <code>1e-11</code> reach the database exactly as they are in PHP</li>
<li><strong>Selection::insert()</strong> with a list of rows returns the number of inserted rows, as documented; code that used the returned ActiveRow now gets an <code>int</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4588325173" data-permission-text="Title is private" data-url="https://github.com/nette/database/issues/330" data-hovercard-type="pull_request" data-hovercard-url="/nette/database/pull/330/hovercard" href="https://github.com/nette/database/pull/330">#330</a>)</li>
<li><strong>transaction()</strong> rethrows the original exception even when the final ROLLBACK fails, e.g. after a deadlock</li>
<li><strong>GroupedSelection::limit()</strong> respects the offset when the selection belongs to multiple parent rows, and a Selection over a table without a primary key can be re-queried</li>
<li>Conditions skipped by a short-circuited <code>?and</code> / <code>?or</code> no longer leave their parameters behind</li>
<li>A <code>where()</code> identical to an existing JOIN condition is no longer dropped, and binary parameters no longer make distinct conditions collide</li>
<li><strong>Row</strong>: <code>isset()</code> and <code>offsetExists()</code> give correct answers, including for falsy values</li>
<li>Reflection is more accurate across drivers: column order of composite foreign keys and indexes (MySQL, PostgreSQL), column defaults (PostgreSQL, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4350332173" data-permission-text="Title is private" data-url="https://github.com/nette/database/issues/329" data-hovercard-type="issue" data-hovercard-url="/nette/database/issues/329/hovercard" href="https://github.com/nette/database/issues/329">#329</a>), primary key and identity columns (MS SQL), tables without an explicit schema (MS SQL), autoincrement detection (SQLite) and table resolution along <code>search_path</code> (PostgreSQL)</li>
<li>MS SQL: identifiers containing <code>[</code> or <code>]</code> are escaped correctly, and offset-only or zero-limit queries generate valid SQL</li>
<li>The Tracy panel no longer shows duplicate BlueScreen SQL sections with multiple connections</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Constraint violations on SQL Server, CHECK violations on SQLite and more connection-loss codes on PostgreSQL and MySQL now map to the specific exception classes</li>
<li>Misuse reports a clear exception instead of a PHP error: an unknown PDO driver, <code>page()</code> with less than one item per page, <code>related()</code> on a composite primary key, <code>getInsertId()</code> on a failed lazy connection, an unknown table in Reflection on SQLite, an unknown constant in the DI options; the ambiguous-reference message names the table, key and candidates</li>
<li>The DI extension detects a single connection by the presence of <code>dsn</code>, so key order in the config no longer matters</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 27 Oct 2026 21:50:45 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/database/releases/tag/v3.2.10</guid>
	</item>
	<item>
		<title>Caching v3.4.3</title>
		<link>https://github.com/nette/caching/releases/tag/v3.4.3</link>
		<description>✨ New Features

Ready for PHP 8.6
SQLiteStorage now cleans up after itself – expired items are removed by probabilistic garbage collection, just like in FileStorage (#83)

🐛 Bug Fixes

FileStorage: an Items dependency on an item that is being generated at the same moment no longer hangs the process (#54)
FileStorage: cleaning the cache leaves alone files and directories of other tools sharing the cache directory, such as Latte, and copes safely with any foreign file it comes across (#45)
MemcachedStorage: items with an expiration longer than 30 days are now kept for the intended time
SQLiteStorage: bulkRead() works with any number of keys, regardless of the SQLite limit of query parameters

🛡️ Robustness

PsrCacheAdapter follows PSR-16 more closely: a zero or negative TTL deletes the item, and a DateInterval TTL is converted independently of the timezone
Edge cases in storages: a non-positive expiration in MemcachedStorage removes the item, SQLiteJournal keeps priority 0, SQLiteStorage ignores Sliding without Expire like the other storages, and SQLite transactions are rolled back on failure
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>Ready for PHP 8.6</li>
<li><strong>SQLiteStorage</strong> now cleans up after itself – expired items are removed by probabilistic garbage collection, just like in FileStorage (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3141852516" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/83" data-hovercard-type="issue" data-hovercard-url="/nette/caching/issues/83/hovercard" href="https://github.com/nette/caching/issues/83">#83</a>)</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>FileStorage: an <code>Items</code> dependency on an item that is being generated at the same moment no longer hangs the process (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="294199391" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/54" data-hovercard-type="issue" data-hovercard-url="/nette/caching/issues/54/hovercard" href="https://github.com/nette/caching/issues/54">#54</a>)</li>
<li>FileStorage: cleaning the cache leaves alone files and directories of other tools sharing the cache directory, such as Latte, and copes safely with any foreign file it comes across (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="174887353" data-permission-text="Title is private" data-url="https://github.com/nette/caching/issues/45" data-hovercard-type="issue" data-hovercard-url="/nette/caching/issues/45/hovercard" href="https://github.com/nette/caching/issues/45">#45</a>)</li>
<li>MemcachedStorage: items with an expiration longer than 30 days are now kept for the intended time</li>
<li>SQLiteStorage: <code>bulkRead()</code> works with any number of keys, regardless of the SQLite limit of query parameters</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li><strong>PsrCacheAdapter</strong> follows PSR-16 more closely: a zero or negative TTL deletes the item, and a <code>DateInterval</code> TTL is converted independently of the timezone</li>
<li>Edge cases in storages: a non-positive expiration in MemcachedStorage removes the item, SQLiteJournal keeps priority 0, SQLiteStorage ignores <code>Sliding</code> without <code>Expire</code> like the other storages, and SQLite transactions are rolled back on failure</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 27 Oct 2026 18:41:44 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/caching/releases/tag/v3.4.3</guid>
	</item>
	<item>
		<title>Mail v4.2.2</title>
		<link>https://github.com/nette/mail/releases/tag/v4.2.2</link>
		<description>
Support for PHP 8.6
The [[...]] placeholder in HTML bodies now embeds only an image inside the base path given to embedImages(); any other [[...]] in the text, such as [[spoiler]] or a path leading outside the base directory, stays as plain text (#108)
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Support for PHP 8.6</li>
<li>The <code>[[...]]</code> placeholder in HTML bodies now embeds only an image inside the base path given to <code>embedImages()</code>; any other <code>[[...]]</code> in the text, such as <code>[[spoiler]]</code> or a path leading outside the base directory, stays as plain text (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5688138628" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/108" data-hovercard-type="pull_request" data-hovercard-url="/nette/mail/pull/108/hovercard" href="https://github.com/nette/mail/pull/108">#108</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 27 Oct 2026 09:48:10 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.2.2</guid>
	</item>
	<item>
		<title>Component Model v4.0.2</title>
		<link>https://github.com/nette/component-model/releases/tag/v4.0.2</link>
		<description>
Supports PHP 8.6
Removed the internal _isCloning() method; no code outside the library calls it
lookup() and lookupPath() always answer from the current tree: the root is found correctly after the tree is attached higher up, and a cloned component finds its cloned ancestors instead of the original ones
An exception thrown from a monitor() callback now cancels the change cleanly: the component stays where it was and the callbacks that already ran get their counterpart, which is what forbidding a form nested in another form relies on
Callbacks that change the tree themselves – remove or move their own component, a sibling or an ancestor – keep the tree, lookup() and the attached/detached notifications consistent
removeComponent() detaches the component before dropping it from the container, so $detached callbacks still see it in its place, and lookup() inside them still finds the ancestor being left
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Supports <strong>PHP 8.6</strong></li>
<li>Removed the internal <strong>_isCloning()</strong> method; no code outside the library calls it</li>
<li><strong>lookup()</strong> and <strong>lookupPath()</strong> always answer from the current tree: the root is found correctly after the tree is attached higher up, and a cloned component finds its cloned ancestors instead of the original ones</li>
<li>An exception thrown from a <strong>monitor()</strong> callback now cancels the change cleanly: the component stays where it was and the callbacks that already ran get their counterpart, which is what forbidding a form nested in another form relies on</li>
<li>Callbacks that change the tree themselves – remove or move their own component, a sibling or an ancestor – keep the tree, <code>lookup()</code> and the attached/detached notifications consistent</li>
<li><strong>removeComponent()</strong> detaches the component before dropping it from the container, so <code>$detached</code> callbacks still see it in its place, and <code>lookup()</code> inside them still finds the ancestor being left</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 27 Oct 2026 01:44:34 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/component-model/releases/tag/v4.0.2</guid>
	</item>
	<item>
		<title>Tester v2.7.0</title>
		<link>https://github.com/nette/tester/releases/tag/v2.7.0</link>
		<description>Tester 2.7 makes itself at home in CI: failures land right in the pull request diff, hanging tests no longer hang the pipeline, and slow tests have nowhere to hide.
✨ New Features

GitHub Actions annotations – the new -o github output marks failed tests directly in the PR diff view, and it switches on automatically when Tester runs on GitHub Actions, so there is nothing to configure
Test time limit – --timeout &lt;seconds&gt; sets a limit for every test, @timeout overrides it per file; a test that runs over is terminated and reported as a failure instead of blocking the whole run
--slowest – prints the 10 (or as many as you ask for) slowest tests after the run, so you know exactly where the time goes
#[DataProvider] and #[Throws] attributes – TestCase methods can now use PHP attributes instead of docblock annotations; the annotations keep working
HttpAssert::fetch() accepts a timeout (30 seconds by default), so an unresponsive server can&apos;t stall a test
JUnit reports now include test durations, for failed and skipped tests as well
Faster cold start – TestCase methods are discovered in parallel with other tests, and each test file&apos;s annotations are parsed only once

💥 Breaking Changes

PHP 8.1 is now the minimum required version
Environment::skip(), Environment::exit() and TestCase::skip() now return never; a subclass overriding them must change its return type too
The tester command exits with a non-zero code when it finds no tests, so a mistyped path no longer passes in CI
A TestCase data provider that returns no data sets is now an error, just like an empty file-level provider
Assertion type &apos;integer&apos; in Assert::type() is deprecated, use &apos;int&apos;

🐛 Bug Fixes

TAP and JUnit outputs no longer contain ANSI color sequences
Environment::lock() reports an error when the lock directory does not exist
</description>
		<content:encoded><![CDATA[
		<p>Tester 2.7 makes itself at home in CI: failures land right in the pull request diff, hanging tests no longer hang the pipeline, and slow tests have nowhere to hide.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>GitHub Actions annotations</strong> – the new <code>-o github</code> output marks failed tests directly in the PR diff view, and it switches on automatically when Tester runs on GitHub Actions, so there is nothing to configure</li>
<li><strong>Test time limit</strong> – <code>--timeout &lt;seconds&gt;</code> sets a limit for every test, <code>@timeout</code> overrides it per file; a test that runs over is terminated and reported as a failure instead of blocking the whole run</li>
<li><strong><code>--slowest</code></strong> – prints the 10 (or as many as you ask for) slowest tests after the run, so you know exactly where the time goes</li>
<li><strong><code>#[DataProvider]</code> and <code>#[Throws]</code> attributes</strong> – <code>TestCase</code> methods can now use PHP attributes instead of docblock annotations; the annotations keep working</li>
<li><strong><code>HttpAssert::fetch()</code></strong> accepts a <code>timeout</code> (30 seconds by default), so an unresponsive server can't stall a test</li>
<li><strong>JUnit reports</strong> now include test durations, for failed and skipped tests as well</li>
<li><strong>Faster cold start</strong> – <code>TestCase</code> methods are discovered in parallel with other tests, and each test file's annotations are parsed only once</li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>PHP 8.1</strong> is now the minimum required version</li>
<li><code>Environment::skip()</code>, <code>Environment::exit()</code> and <code>TestCase::skip()</code> now return <code>never</code>; a subclass overriding them must change its return type too</li>
<li>The <code>tester</code> command exits with a non-zero code when it finds no tests, so a mistyped path no longer passes in CI</li>
<li>A <code>TestCase</code> data provider that returns no data sets is now an error, just like an empty file-level provider</li>
<li>Assertion type <code>'integer'</code> in <code>Assert::type()</code> is deprecated, use <code>'int'</code></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>TAP and JUnit outputs no longer contain ANSI color sequences</li>
<li><code>Environment::lock()</code> reports an error when the lock directory does not exist</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 26 Oct 2026 22:25:40 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tester/releases/tag/v2.7.0</guid>
	</item>
	<item>
		<title>Php Generator v4.2.4</title>
		<link>https://github.com/nette/php-generator/releases/tag/v4.2.4</link>
		<description>🐛 Bug Fixes

fromCode() now keeps a file comment placed before declare(strict_types=1) (#182)
Extracting method and property hook bodies ignores the members of anonymous classes nested inside them
PropertyHookType is now an alias of PropertyAccessMode, so both enums are interchangeable wherever hooks are added or looked up

🛡️ Robustness

Invalid declarations now report a clear error when printed: a readonly property that is static or has a default value, a final private constant, an abstract final property hook, and an enum whose backing type is not int or string or whose case values do not match it
setHooks() validates hook types, and the presence of php-parser 5 is detected reliably, with a clear message when an older version is installed
</description>
		<content:encoded><![CDATA[
		<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>fromCode()</code> now keeps a file comment placed before <code>declare(strict_types=1)</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4017794327" data-permission-text="Title is private" data-url="https://github.com/nette/php-generator/issues/182" data-hovercard-type="pull_request" data-hovercard-url="/nette/php-generator/pull/182/hovercard" href="https://github.com/nette/php-generator/pull/182">#182</a>)</li>
<li>Extracting method and property hook bodies ignores the members of anonymous classes nested inside them</li>
<li><code>PropertyHookType</code> is now an alias of <code>PropertyAccessMode</code>, so both enums are interchangeable wherever hooks are added or looked up</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Invalid declarations now report a clear error when printed: a readonly property that is static or has a default value, a <code>final private</code> constant, an <code>abstract final</code> property hook, and an enum whose backing type is not int or string or whose case values do not match it</li>
<li><code>setHooks()</code> validates hook types, and the presence of php-parser 5 is detected reliably, with a clear message when an older version is installed</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 26 Oct 2026 22:18:30 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/php-generator/releases/tag/v4.2.4</guid>
	</item>
	<item>
		<title>Routing v3.1.5</title>
		<link>https://github.com/nette/routing/releases/tag/v3.1.5</link>
		<description>
PHP 8.6 support
RouteList with withDomain() or withPath() no longer keeps growing its internal cache in long-running applications (workers like FrankenPHP or RoadRunner)
constructUrl() with an array or object as a path parameter now skips the route instead of throwing a TypeError
</description>
		<content:encoded><![CDATA[
		<ul>
<li>PHP 8.6 support</li>
<li><code>RouteList</code> with <code>withDomain()</code> or <code>withPath()</code> no longer keeps growing its internal cache in long-running applications (workers like FrankenPHP or RoadRunner)</li>
<li><code>constructUrl()</code> with an array or object as a path parameter now skips the route instead of throwing a <code>TypeError</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 26 Oct 2026 22:00:49 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/routing/releases/tag/v3.1.5</guid>
	</item>
	<item>
		<title>Di v3.2.8</title>
		<link>https://github.com/nette/di/releases/tag/v3.2.8</link>
		<description>✨ New Features

Support for PHP 8.6
Support for nette/neon 4.0: configuration files are read the same way as with 3.x, which keeps working
#[SensitiveParameter] now hides arrays and other non-scalar arguments too, so database credentials passed as an array no longer show up in Tracy&apos;s source snippets
Nette\DI\Definitions\Definition now lives at Nette\DI\Definition; the old name keeps working as an alias

💥 Breaking Changes

Locator definitions are checked at compile time. Every reference must match a get*() or create*() method of the interface, and every method with a non-nullable return type must have its reference. A typo in a key now fails compilation with a message naming the reference or method, where it used to compile and throw MissingServiceException only on the first call. Fix the key, or make the method&apos;s return type nullable if the service is truly optional. Interfaces with a generic get($name) are exempt.
Service names may no longer contain __, which is reserved for encoding dots in the names of generated methods.

🐛 Bug Fixes

Locator methods with an acronym work with the natural key: getPDO() finds the reference pdo (and still pDO), the same for getURL(), getDB() and the like
Container::createInstance() and callMethod() pass the actual value to a scalar parameter marked #[SensitiveParameter]
getServiceDescriptors() reports a service named PDO under its real name instead of pDO
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>Support for PHP 8.6</li>
<li>Support for <strong>nette/neon 4.0</strong>: configuration files are read the same way as with 3.x, which keeps working</li>
<li><strong><code>#[SensitiveParameter]</code> now hides arrays and other non-scalar arguments too</strong>, so database credentials passed as an array no longer show up in Tracy's source snippets</li>
<li><code>Nette\DI\Definitions\Definition</code> now lives at <strong><code>Nette\DI\Definition</code></strong>; the old name keeps working as an alias</li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>Locator definitions are checked at compile time.</strong> Every reference must match a <code>get*()</code> or <code>create*()</code> method of the interface, and every method with a non-nullable return type must have its reference. A typo in a key now fails compilation with a message naming the reference or method, where it used to compile and throw <code>MissingServiceException</code> only on the first call. Fix the key, or make the method's return type nullable if the service is truly optional. Interfaces with a generic <code>get($name)</code> are exempt.</li>
<li>Service names may no longer contain <code>__</code>, which is reserved for encoding dots in the names of generated methods.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Locator methods with an acronym work with the natural key: <code>getPDO()</code> finds the reference <code>pdo</code> (and still <code>pDO</code>), the same for <code>getURL()</code>, <code>getDB()</code> and the like</li>
<li><code>Container::createInstance()</code> and <code>callMethod()</code> pass the actual value to a scalar parameter marked <code>#[SensitiveParameter]</code></li>
<li><code>getServiceDescriptors()</code> reports a service named <code>PDO</code> under its real name instead of <code>pDO</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 26 Oct 2026 15:50:33 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/di/releases/tag/v3.2.8</guid>
	</item>
	<item>
		<title>Neon v4.0.0</title>
		<link>https://github.com/nette/neon/releases/tag/v4.0.0</link>
		<description>NEON 4 parses a file into a lossless syntax tree in which every comment and every space has its place, so you can edit a configuration and the diff shows only your change. Decoding and encoding stay as they were: Neon::decode() gives the same values as 3.4.
✨ New Features

Lossless parsing – Neon::parse($text)-&gt;print() === $text holds for any input NEON accepts
Format-preserving editing – setValue(), addItem() and removeItem() change only the tokens they edit: 0x0CEA stays hexadecimal, yes becomes no, a new key is indented like its siblings, and a removed item takes its comment along. A refused edit changes nothing at all, so installers, admin panels and AI agents can rewrite config.neon safely
A navigable tree – nodes know their parent, their comments and their position (line, column, offset); find(), findAncestor(), siblings, and a public Traverser that can replace and remove nodes on the walk
Evaluator – subclass it to turn literals, strings or entities into your own values, such as constants or parameters, the way the Nette DI container reads its configuration
Neon::encode() accepts a closure as $blockMode to decide per array whether it is written as a block, e.g. fn($v, $path) =&gt; !$path for the first level only, and writes floats in the shortest form that reads back exactly
Exception carries the position of the problem as an object and the bare message via getDescription()
neon-lint reports one line per finding, --json for tools and --check to verify that a file prints back byte for byte; an AI agent can run it after saving a .neon file
Runnable examples with their real output document the whole API
The format, the tree and the editing semantics follow a language-neutral specification shared with the JavaScript implementation @nette/neon

💥 Breaking Changes

Requires PHP 8.4 or newer and the mbstring extension
The tree API is new: Neon::parse() returns a Nodes\DocumentNode, and the classes Decoder, Node\* and the old Traverser are gone. Code that walked the old nodes moves to the new tree, see examples/tree
Neon::encode() throws Nette\Neon\Exception for a string that is not valid UTF-8 instead of replacing it with U+FFFD; its errors now name the path to the value
Some error messages are more precise; code that matches their text may need an update
neon-lint has a new command-line contract: --debug is gone, and a failure of the tool itself exits with 2
Neon::BLOCK and Neon::CHAIN are deprecated, use blockMode: true and Neon::Chain
</description>
		<content:encoded><![CDATA[
		<p>NEON 4 parses a file into a lossless syntax tree in which every comment and every space has its place, so you can edit a configuration and the diff shows only your change. Decoding and encoding stay as they were: <code>Neon::decode()</code> gives the same values as 3.4.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>Lossless parsing</strong> – <code>Neon::parse($text)-&gt;print() === $text</code> holds for any input NEON accepts</li>
<li><strong>Format-preserving editing</strong> – <code>setValue()</code>, <code>addItem()</code> and <code>removeItem()</code> change only the tokens they edit: <code>0x0CEA</code> stays hexadecimal, <code>yes</code> becomes <code>no</code>, a new key is indented like its siblings, and a removed item takes its comment along. A refused edit changes nothing at all, so installers, admin panels and AI agents can rewrite <code>config.neon</code> safely</li>
<li><strong>A navigable tree</strong> – nodes know their parent, their comments and their position (line, column, offset); <code>find()</code>, <code>findAncestor()</code>, siblings, and a public <strong>Traverser</strong> that can replace and remove nodes on the walk</li>
<li><strong>Evaluator</strong> – subclass it to turn literals, strings or entities into your own values, such as constants or parameters, the way the Nette DI container reads its configuration</li>
<li><strong>Neon::encode()</strong> accepts a closure as <code>$blockMode</code> to decide per array whether it is written as a block, e.g. <code>fn($v, $path) =&gt; !$path</code> for the first level only, and writes floats in the shortest form that reads back exactly</li>
<li><strong>Exception</strong> carries the position of the problem as an object and the bare message via <code>getDescription()</code></li>
<li><strong>neon-lint</strong> reports one line per finding, <code>--json</code> for tools and <code>--check</code> to verify that a file prints back byte for byte; an AI agent can run it after saving a <code>.neon</code> file</li>
<li>Runnable <a target=_blank rel=noopener href="/nette/neon/blob/v4.0.0/examples">examples</a> with their real output document the whole API</li>
<li>The format, the tree and the editing semantics follow a language-neutral <a target=_blank rel=noopener href="https://github.com/nette/neon-specification">specification</a> shared with the JavaScript implementation <a target=_blank rel=noopener href="https://github.com/nette/neon-js">@nette/neon</a></li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li>Requires PHP 8.4 or newer and the <code>mbstring</code> extension</li>
<li>The tree API is new: <strong>Neon::parse()</strong> returns a <code>Nodes\DocumentNode</code>, and the classes <code>Decoder</code>, <code>Node\*</code> and the old <code>Traverser</code> are gone. Code that walked the old nodes moves to the new tree, see <a target=_blank rel=noopener href="/nette/neon/blob/v4.0.0/examples/tree">examples/tree</a></li>
<li><strong>Neon::encode()</strong> throws <code>Nette\Neon\Exception</code> for a string that is not valid UTF-8 instead of replacing it with U+FFFD; its errors now name the path to the value</li>
<li>Some error messages are more precise; code that matches their text may need an update</li>
<li><strong>neon-lint</strong> has a new command-line contract: <code>--debug</code> is gone, and a failure of the tool itself exits with 2</li>
<li><code>Neon::BLOCK</code> and <code>Neon::CHAIN</code> are deprecated, use <code>blockMode: true</code> and <code>Neon::Chain</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 26 Oct 2026 00:19:49 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v4.0.0</guid>
	</item>
	<item>
		<title>Neon v3.4.10</title>
		<link>https://github.com/nette/neon/releases/tag/v3.4.10</link>
		<description>🐛 Bug Fixes

Neon::encode() now quotes strings like -.5 and +.5, so they decode back as strings, not floats
Multiline strings whose first line starts with whitespace, or with a line starting with &apos;&apos;&apos;, now survive an encode and decode round trip unchanged
neon-lint no longer mistakes --debug for the path to check

🛡️ Robustness

The parser holds up against hostile input: nesting deeper than 500 levels throws Too deep nesting instead of overflowing the stack, and deeply nested dash lists no longer take exponential time to parse
Error messages count the column in characters rather than bytes, and their excerpts never cut a multibyte character in half
</description>
		<content:encoded><![CDATA[
		<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>Neon::encode()</strong> now quotes strings like <code>-.5</code> and <code>+.5</code>, so they decode back as strings, not floats</li>
<li>Multiline strings whose first line starts with whitespace, or with a line starting with <code>'''</code>, now survive an encode and decode round trip unchanged</li>
<li><strong>neon-lint</strong> no longer mistakes <code>--debug</code> for the path to check</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>The parser holds up against hostile input: nesting deeper than 500 levels throws <code>Too deep nesting</code> instead of overflowing the stack, and deeply nested dash lists no longer take exponential time to parse</li>
<li>Error messages count the column in characters rather than bytes, and their excerpts never cut a multibyte character in half</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 25 Oct 2026 23:03:38 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v3.4.10</guid>
	</item>
	<item>
		<title>Robot Loader v4.1.4</title>
		<link>https://github.com/nette/robot-loader/releases/tag/v4.1.4</link>
		<description>
RobotLoader is ready for PHP 8.6
</description>
		<content:encoded><![CDATA[
		<ul>
<li>RobotLoader is ready for <strong>PHP 8.6</strong></li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 25 Oct 2026 16:51:42 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/robot-loader/releases/tag/v4.1.4</guid>
	</item>
	<item>
		<title>Http v3.4.2</title>
		<link>https://github.com/nette/http/releases/tag/v3.4.2</link>
		<description>✨ New Features

PHP 8.6 is officially supported
Static analysis now knows that getQuery() and getPost() without a key return an array of all parameters
IResponse::setCookie() declares the $sameSite and $partitioned parameters, so code typed against the interface passes static analysis when using them (#247)

🐛 Bug Fixes

getQuery(null) and getPost(null) return all parameters, the same as calling them without an argument
getDomain() of Url and UrlImmutable returns IPv6 addresses with an embedded IPv4 part ([::ffff:192.0.2.1]) and 0.0.0.0 whole instead of splitting them at the dots (#241)
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>PHP 8.6 is officially supported</li>
<li>Static analysis now knows that <strong>getQuery()</strong> and <strong>getPost()</strong> without a key return an array of all parameters</li>
<li><strong>IResponse::setCookie()</strong> declares the <code>$sameSite</code> and <code>$partitioned</code> parameters, so code typed against the interface passes static analysis when using them (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4066705737" data-permission-text="Title is private" data-url="https://github.com/nette/http/issues/247" data-hovercard-type="pull_request" data-hovercard-url="/nette/http/pull/247/hovercard" href="https://github.com/nette/http/pull/247">#247</a>)</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>getQuery(null)</strong> and <strong>getPost(null)</strong> return all parameters, the same as calling them without an argument</li>
<li><strong>getDomain()</strong> of <code>Url</code> and <code>UrlImmutable</code> returns IPv6 addresses with an embedded IPv4 part (<code>[::ffff:192.0.2.1]</code>) and <code>0.0.0.0</code> whole instead of splitting them at the dots (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2713856379" data-permission-text="Title is private" data-url="https://github.com/nette/http/issues/241" data-hovercard-type="pull_request" data-hovercard-url="/nette/http/pull/241/hovercard" href="https://github.com/nette/http/pull/241">#241</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 23 Oct 2026 13:58:49 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/http/releases/tag/v3.4.2</guid>
	</item>
	<item>
		<title>Http v3.3.5</title>
		<link>https://github.com/nette/http/releases/tag/v3.3.5</link>
		<description>✨ New Features

Ready for PHP 8.6

🐛 Bug Fixes

Security: the client address behind a trusted proxy is now taken from the rightmost untrusted hop of Forwarded / X-Forwarded-For, so a client cannot spoof it by prepending its own entry. Scheme and host are read from that same hop, and getRemoteAddress() returns null when the forwarded value is not a valid IP.
UserStorage::setNamespace() now works when switching to another namespace after the storage has been used
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>Ready for <strong>PHP 8.6</strong></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>Security:</strong> the client address behind a trusted proxy is now taken from the rightmost untrusted hop of <code>Forwarded</code> / <code>X-Forwarded-For</code>, so a client cannot spoof it by prepending its own entry. Scheme and host are read from that same hop, and <code>getRemoteAddress()</code> returns <code>null</code> when the forwarded value is not a valid IP.</li>
<li><code>UserStorage::setNamespace()</code> now works when switching to another namespace after the storage has been used</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 23 Oct 2026 13:19:12 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/http/releases/tag/v3.3.5</guid>
	</item>
	<item>
		<title>Tester v2.6.3</title>
		<link>https://github.com/nette/tester/releases/tag/v2.6.3</link>
		<description>✨ New Features

Runner now warns you when Xdebug is active and slows the whole run down many times over, so a forgotten xdebug.mode no longer quietly costs you minutes (no warning when Xdebug serves as the code coverage engine)

🐛 Bug Fixes

FileMock is ready for PHP 8.6
Call arguments in stack traces stay on a single line even when strings contain newlines or tabs
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li>Runner now warns you when Xdebug is active and slows the whole run down many times over, so a forgotten <code>xdebug.mode</code> no longer quietly costs you minutes (no warning when Xdebug serves as the code coverage engine)</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>FileMock</strong> is ready for PHP 8.6</li>
<li>Call arguments in stack traces stay on a single line even when strings contain newlines or tabs</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 23 Oct 2026 11:22:45 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tester/releases/tag/v2.6.3</guid>
	</item>
	<item>
		<title>Neon v3.4.9</title>
		<link>https://github.com/nette/neon/releases/tag/v3.4.9</link>
		<description>
PHP 8.6 is supported
A literal shaped like a date that is not a valid one, such as 2024-02-30 or 2024-13-01, now decodes as a plain string
The entity name !!chain is reserved for chained entities and can no longer be written in the input
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>PHP 8.6</strong> is supported</li>
<li>A literal shaped like a date that is not a valid one, such as <code>2024-02-30</code> or <code>2024-13-01</code>, now decodes as a plain string</li>
<li>The entity name <code>!!chain</code> is reserved for chained entities and can no longer be written in the input</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 02:50:07 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v3.4.9</guid>
	</item>
	<item>
		<title>Security v3.2.7</title>
		<link>https://github.com/nette/security/releases/tag/v3.2.7</link>
		<description>✨ New Features

PHP 8.6 is now supported

🐛 Bug Fixes

The authenticator defined by security: users: in NEON is now autowired to services that require Nette\Security\Authenticator
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>PHP 8.6</strong> is now supported</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>The authenticator defined by <code>security: users:</code> in NEON is now autowired to services that require <code>Nette\Security\Authenticator</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 02:40:03 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/security/releases/tag/v3.2.7</guid>
	</item>
	<item>
		<title>Schema v1.4.0</title>
		<link>https://github.com/nette/schema/releases/tag/v1.4.0</link>
		<description>Your schema can now be the documentation of your configuration: give elements a
description, export the schema as JSON Schema, and editors offer completion, explain
each option and underline mistakes right in the config file.
✨ New Features

JsonSchema::export() – turns a schema into a JSON Schema
document, the format editors read to validate and complete JSON or YAML files. It exports
types, ranges, patterns, required items, enum values and descriptions. A type that exists
only in PHP, such as a class, throws NotSupportedException instead of exporting something
the schema would not accept.
description() – attach a human-readable description to any element. It does not affect
validation, and it travels into the JSON Schema export.
Expect::enum() – stop hand-rolling the conversion of backed enums:
Expect::enum(Suit::class) accepts the backing value or the case itself and always gives
you the case. An enum-typed property in Expect::from() maps to it automatically.
Expect::type(Suit::class) keeps meaning plain instanceof, as for any other class.
Expect::tuple() – a fixed-size list where each position has its own schema:
Expect::tuple([Expect::string(), Expect::int()]). otherItems() describes the rest
elements, extend() appends positions, and when configurations are layered, a later tuple
replaces the earlier one as a whole.
Expect::listOf() with wrap – Expect::listOf(&apos;string&apos;, wrap: true) also accepts a single
value and wraps it into a one-item list, so both email: foo@example.com and
email: [a@example.com, b@example.com] work.
mergeMode() and mergeWith() – say in the schema how layered configurations combine
instead of relying on the deep merge: Expect::arrayOf(&apos;string&apos;)-&gt;mergeMode(MergeMode::Replace)
takes the later array as a whole, while OverwriteKeys and AppendKeys merge by keys. Any
element can get its own combining function, such as
Expect::bool()-&gt;mergeWith(fn($value, $base) =&gt; $value || $base). A schema without them
merges exactly as before, and the same calls keep working in 2.0.
castTo(&apos;?type&apos;) – castTo(&apos;?string&apos;) keeps a null and casts everything else. A class
or an enum keeps the null even without the question mark, so
Expect::string()-&gt;nullable()-&gt;castTo(DateTime::class) just works.
Kind-specific element classes – Expect::string() returns a StringType, Expect::int()
a NumberType, Expect::listOf() an ArrayType, so your IDE and PHPStan know which options
each element has. They are subclasses of Type, so existing code keeps working.

⚠️ Deprecations

before() called repeatedly – a second before() on the same element still replaces the
first one, but raises a notice: in 2.0 the handlers will chain in declaration order. Merge
them into one.
&apos;?int[]&apos; – in 1.x it means an array of nullable items, while 2.0 reads it as a nullable
array, as phpDoc does. The notice names the replacement that keeps the meaning:
Expect::arrayOf(Expect::type(&apos;int&apos;)-&gt;nullable()).
Options that do not fit the element – min(), max(), pattern(), items() and
mergeDefaults() on a union such as Expect::type(&apos;int|string&apos;) belong to the variants:
Expect::anyOf(Expect::int()-&gt;min(1), Expect::string()-&gt;min(1)). Likewise pattern() on a
number or an array, items() on a string or a number and mergeDefaults() on anything but
an array raise a notice.

🐛 Bug Fixes

A nullable anyOf() containing a structure or an array gives null for a null input,
wherever the null sits among the variants.
Smaller fixes: anyOf()-&gt;deprecated() emits its warning, min() and max() keep the
precision of large integer bounds, and the internal _prevent_merging marker no longer
appears in the output of a structure.
</description>
		<content:encoded><![CDATA[
		<p>Your schema can now be the documentation of your configuration: give elements a<br>
description, export the schema as JSON Schema, and editors offer completion, explain<br>
each option and underline mistakes right in the config file.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>JsonSchema::export()</strong> – turns a schema into a <a target=_blank rel=noopener href="https://json-schema.org" rel="nofollow">JSON Schema</a><br>
document, the format editors read to validate and complete JSON or YAML files. It exports<br>
types, ranges, patterns, required items, enum values and descriptions. A type that exists<br>
only in PHP, such as a class, throws <code>NotSupportedException</code> instead of exporting something<br>
the schema would not accept.</li>
<li><strong>description()</strong> – attach a human-readable description to any element. It does not affect<br>
validation, and it travels into the JSON Schema export.</li>
<li><strong>Expect::enum()</strong> – stop hand-rolling the conversion of backed enums:<br>
<code>Expect::enum(Suit::class)</code> accepts the backing value or the case itself and always gives<br>
you the case. An enum-typed property in <code>Expect::from()</code> maps to it automatically.<br>
<code>Expect::type(Suit::class)</code> keeps meaning plain <code>instanceof</code>, as for any other class.</li>
<li><strong>Expect::tuple()</strong> – a fixed-size list where each position has its own schema:<br>
<code>Expect::tuple([Expect::string(), Expect::int()])</code>. <code>otherItems()</code> describes the rest<br>
elements, <code>extend()</code> appends positions, and when configurations are layered, a later tuple<br>
replaces the earlier one as a whole.</li>
<li><strong>Expect::listOf() with wrap</strong> – <code>Expect::listOf('string', wrap: true)</code> also accepts a single<br>
value and wraps it into a one-item list, so both <code>email: foo@example.com</code> and<br>
<code>email: [a@example.com, b@example.com]</code> work.</li>
<li><strong>mergeMode() and mergeWith()</strong> – say in the schema how layered configurations combine<br>
instead of relying on the deep merge: <code>Expect::arrayOf('string')-&gt;mergeMode(MergeMode::Replace)</code><br>
takes the later array as a whole, while <code>OverwriteKeys</code> and <code>AppendKeys</code> merge by keys. Any<br>
element can get its own combining function, such as<br>
<code>Expect::bool()-&gt;mergeWith(fn($value, $base) =&gt; $value || $base)</code>. A schema without them<br>
merges exactly as before, and the same calls keep working in 2.0.</li>
<li><strong>castTo('?type')</strong> – <code>castTo('?string')</code> keeps a <code>null</code> and casts everything else. A class<br>
or an enum keeps the <code>null</code> even without the question mark, so<br>
<code>Expect::string()-&gt;nullable()-&gt;castTo(DateTime::class)</code> just works.</li>
<li><strong>Kind-specific element classes</strong> – <code>Expect::string()</code> returns a <code>StringType</code>, <code>Expect::int()</code><br>
a <code>NumberType</code>, <code>Expect::listOf()</code> an <code>ArrayType</code>, so your IDE and PHPStan know which options<br>
each element has. They are subclasses of <code>Type</code>, so existing code keeps working.</li>
</ul>
<h2><g-emoji class="g-emoji" alias="warning">⚠️</g-emoji> Deprecations</h2>
<ul>
<li><strong>before() called repeatedly</strong> – a second <code>before()</code> on the same element still replaces the<br>
first one, but raises a notice: in 2.0 the handlers will chain in declaration order. Merge<br>
them into one.</li>
<li><strong>'?int[]'</strong> – in 1.x it means an array of nullable items, while 2.0 reads it as a nullable<br>
array, as phpDoc does. The notice names the replacement that keeps the meaning:<br>
<code>Expect::arrayOf(Expect::type('int')-&gt;nullable())</code>.</li>
<li><strong>Options that do not fit the element</strong> – <code>min()</code>, <code>max()</code>, <code>pattern()</code>, <code>items()</code> and<br>
<code>mergeDefaults()</code> on a union such as <code>Expect::type('int|string')</code> belong to the variants:<br>
<code>Expect::anyOf(Expect::int()-&gt;min(1), Expect::string()-&gt;min(1))</code>. Likewise <code>pattern()</code> on a<br>
number or an array, <code>items()</code> on a string or a number and <code>mergeDefaults()</code> on anything but<br>
an array raise a notice.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>A nullable <code>anyOf()</code> containing a structure or an array gives <code>null</code> for a <code>null</code> input,<br>
wherever the <code>null</code> sits among the variants.</li>
<li>Smaller fixes: <code>anyOf()-&gt;deprecated()</code> emits its warning, <code>min()</code> and <code>max()</code> keep the<br>
precision of large integer bounds, and the internal <code>_prevent_merging</code> marker no longer<br>
appears in the output of a structure.</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 02:22:13 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/schema/releases/tag/v1.4.0</guid>
	</item>
	<item>
		<title>Php Generator v4.2.3</title>
		<link>https://github.com/nette/php-generator/releases/tag/v4.2.3</link>
		<description>✨ New Features

PHP 8.6 is now supported

🐛 Bug Fixes

Loading a class with ClassType::from() or fromCode() now keeps the types of typed class constants (PHP 8.3)
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>PHP 8.6</strong> is now supported</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Loading a class with <code>ClassType::from()</code> or <code>fromCode()</code> now keeps the types of typed class constants (PHP 8.3)</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 01:14:46 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/php-generator/releases/tag/v4.2.3</guid>
	</item>
	<item>
		<title>Latte v3.0.27</title>
		<link>https://github.com/nette/latte/releases/tag/v3.0.27</link>
		<description>
PHP 8.6 support
A template with a multi-line name compiles to valid PHP
</description>
		<content:encoded><![CDATA[
		<ul>
<li>PHP 8.6 support</li>
<li>A template with a multi-line name compiles to valid PHP</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 00:50:46 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.0.27</guid>
	</item>
	<item>
		<title>Latte v3.1.7</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.7</link>
		<description>💥 Breaking Changes

contenteditable, draggable, spellcheck, hidden are no longer treated as plain boolean attributes, because in HTML they are not. contenteditable={$editable} now renders contenteditable=&quot;true&quot; or contenteditable=&quot;false&quot;, so false really turns editing off instead of silently inheriting it from the parent, and draggable can be set to true at all. hidden and popover stay flags but keep a value, so hidden=&quot;until-found&quot; survives. With migration warnings on, Latte reports every place where the output changes; use |toggle to keep the old bare-name rendering
Sandbox – property names in a policy are case-sensitive, as they are in PHP: allowing visible no longer allows Visible
isPartialFunction() of the call nodes is renamed to isPartialApplication() – only matters for extensions working with the AST

✨ New Features

PHP 8.6 support
NodeHelpers::find() and findFirst() accept a node class as the filter: find($node, TextNode::class) returns a list&lt;TextNode&gt;, no type annotation needed
ExpressionNode::toValue() and hasValue() tell an extension whether an expression is a literal value and which; NodeHelpers::toValue() is deprecated in their favor

🔒 Security

The sandbox got a thorough review of its runtime checks: a dynamic property name is evaluated just once, so it cannot be checked with one value and accessed with another; (array) cast of an object is forbidden and foreach over an object checks its properties against the policy; $iterator no longer passes calls of unknown methods to the iterated object; and -&gt; / ?-&gt; method calls behave exactly as in PHP
A &lt;script&gt; whose type is anything the browser might execute (e.g. text/javascript1.5) is escaped as JavaScript; only a plain data type such as text/csv is escaped as text, and text/html or text/x-template as HTML
A custom sandbox policy without getCacheSignature() triggers a deprecation, because its instances with different rules would share compiled templates

🐛 Bug Fixes

{include parent} restores the block level after an exception and works in a block that includes itself
{capture $a[$i++]|filter} evaluates its target once
|slice with a negative start or length works on iterators the same way as on arrays, and |batch keeps every item of an iterator with repeated keys
An arrow function body swallows and, or and xor, as in PHP
The deprecation of an unqualified constant is no longer raised for class names written in capitals such as FOO::bar() or new FOO

🛡️ Robustness

Writing through ?-&gt; anywhere in a chain ($a?-&gt;b-&gt;c = 1) is a compile error instead of a PHP error later
The linter writes errors to stderr outside CLI too and restores its error handler for an unreadable file
</description>
		<content:encoded><![CDATA[
		<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>contenteditable, draggable, spellcheck, hidden</strong> are no longer treated as plain boolean attributes, because in HTML they are not. <code>contenteditable={$editable}</code> now renders <code>contenteditable="true"</code> or <code>contenteditable="false"</code>, so <code>false</code> really turns editing off instead of silently inheriting it from the parent, and <code>draggable</code> can be set to <code>true</code> at all. <code>hidden</code> and <code>popover</code> stay flags but keep a value, so <code>hidden="until-found"</code> survives. With migration warnings on, Latte reports every place where the output changes; use <code>|toggle</code> to keep the old bare-name rendering</li>
<li><strong>Sandbox</strong> – property names in a policy are case-sensitive, as they are in PHP: allowing <code>visible</code> no longer allows <code>Visible</code></li>
<li><strong>isPartialFunction()</strong> of the call nodes is renamed to <strong>isPartialApplication()</strong> – only matters for extensions working with the AST</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li>PHP 8.6 support</li>
<li><strong>NodeHelpers::find()</strong> and <strong>findFirst()</strong> accept a node class as the filter: <code>find($node, TextNode::class)</code> returns a <code>list&lt;TextNode&gt;</code>, no type annotation needed</li>
<li><strong>ExpressionNode::toValue()</strong> and <strong>hasValue()</strong> tell an extension whether an expression is a literal value and which; <code>NodeHelpers::toValue()</code> is deprecated in their favor</li>
</ul>
<h2>🔒 Security</h2>
<ul>
<li>The sandbox got a thorough review of its runtime checks: a dynamic property name is evaluated just once, so it cannot be checked with one value and accessed with another; <code>(array)</code> cast of an object is forbidden and <code>foreach</code> over an object checks its properties against the policy; <code>$iterator</code> no longer passes calls of unknown methods to the iterated object; and <code>-&gt;</code> / <code>?-&gt;</code> method calls behave exactly as in PHP</li>
<li>A <code>&lt;script&gt;</code> whose <code>type</code> is anything the browser might execute (e.g. <code>text/javascript1.5</code>) is escaped as JavaScript; only a plain data type such as <code>text/csv</code> is escaped as text, and <code>text/html</code> or <code>text/x-template</code> as HTML</li>
<li>A custom sandbox policy without <code>getCacheSignature()</code> triggers a deprecation, because its instances with different rules would share compiled templates</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>{include parent}</code> restores the block level after an exception and works in a block that includes itself</li>
<li><code>{capture $a[$i++]|filter}</code> evaluates its target once</li>
<li><code>|slice</code> with a negative start or length works on iterators the same way as on arrays, and <code>|batch</code> keeps every item of an iterator with repeated keys</li>
<li>An arrow function body swallows <code>and</code>, <code>or</code> and <code>xor</code>, as in PHP</li>
<li>The deprecation of an unqualified constant is no longer raised for class names written in capitals such as <code>FOO::bar()</code> or <code>new FOO</code></li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Writing through <code>?-&gt;</code> anywhere in a chain (<code>$a?-&gt;b-&gt;c = 1</code>) is a compile error instead of a PHP error later</li>
<li>The linter writes errors to stderr outside CLI too and restores its error handler for an unreadable file</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Oct 2026 00:11:30 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.7</guid>
	</item>
	<item>
		<title>Tracy v2.12.2</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.12.2</link>
		<description>
PHP 8.6 – Tracy is ready for the upcoming PHP version
BlueScreen – the markdown output (for agents and the .md files saved next to logged exceptions) now masks sensitive regions in source snippets just like the HTML page does, such as #[\SensitiveParameter] values in the compiled DI container (thx @spaze)
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>PHP 8.6</strong> – Tracy is ready for the upcoming PHP version</li>
<li><strong>BlueScreen</strong> – the markdown output (for agents and the <code>.md</code> files saved next to logged exceptions) now masks sensitive regions in source snippets just like the HTML page does, such as <code>#[\SensitiveParameter]</code> values in the compiled DI container (thx <a target=_blank rel=noopener class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/spaze/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/spaze">@spaze</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 21 Oct 2026 23:25:00 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.12.2</guid>
	</item>
	<item>
		<title>Utils v4.0.11</title>
		<link>https://github.com/nette/utils/releases/tag/v4.0.11</link>
		<description>
PHP 8.6 is supported, so Nette Utils 4.0 now covers PHP 8.0 to 8.6
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>PHP 8.6</strong> is supported, so Nette Utils 4.0 now covers PHP 8.0 to 8.6</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 21 Oct 2026 16:53:25 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.0.11</guid>
	</item>
	<item>
		<title>Utils v4.1.6</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.6</link>
		<description>A small maintenance release: PHP 8.6 support and one fix for paths with a scheme.
✨ New Features

PHP 8.6 is supported

🐛 Bug Fixes

FileSystem::normalizePath(), joinPaths() and resolvePath() keep the scheme of paths like phar://
</description>
		<content:encoded><![CDATA[
		<p>A small maintenance release: PHP 8.6 support and one fix for paths with a scheme.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>PHP 8.6</strong> is supported</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>FileSystem::normalizePath()</strong>, <code>joinPaths()</code> and <code>resolvePath()</code> keep the scheme of paths like <code>phar://</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 20 Oct 2026 17:48:48 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.6</guid>
	</item>
	<item>
		<title>Schema v1.3.7</title>
		<link>https://github.com/nette/schema/releases/tag/v1.3.7</link>
		<description>A maintenance release: PHP 8.6 support, a nicer way to write defaults, and a few edge cases that now fail with a clear message instead of a confusing one.
✨ New Features

PHP 8.6 is supported
Defaults can be passed as a named argument: Expect::string(default: &apos;abc&apos;)

🛡️ Robustness

Mistakes in a schema now report a clear error: an invalid regex pattern, a variadic constructor in Expect::from(), or a key transformed into something that cannot be a key
Expect::from() ignores non-public and static properties
Calling process() recursively on the same Processor instance works correctly
</description>
		<content:encoded><![CDATA[
		<p>A maintenance release: PHP 8.6 support, a nicer way to write defaults, and a few edge cases that now fail with a clear message instead of a confusing one.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>PHP 8.6</strong> is supported</li>
<li>Defaults can be passed as a named argument: <code>Expect::string(default: 'abc')</code></li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Mistakes in a schema now report a clear error: an invalid regex pattern, a variadic constructor in <code>Expect::from()</code>, or a key transformed into something that cannot be a key</li>
<li><code>Expect::from()</code> ignores non-public and static properties</li>
<li>Calling <code>process()</code> recursively on the same <code>Processor</code> instance works correctly</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 20 Oct 2026 15:48:27 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/schema/releases/tag/v1.3.7</guid>
	</item>
	<item>
		<title>Tester v2.6.2</title>
		<link>https://github.com/nette/tester/releases/tag/v2.6.2</link>
		<description>✨ New Features

TestCase::run() runs every test method even after one fails, so a single run shows you all failures at once: results first, details of each failure after them (#469)
Stack traces show call arguments, so you see right away which call failed: redirect(&apos;https://…&apos;, 302) instead of a bare redirect()
PHP 8.6 support

🐛 Bug Fixes

@phpVersion handles the boundary versions correctly: @phpVersion 8.4.3 runs on PHP 8.4.3 and &lt; 8.0 no longer runs on 8.0; common forms like @phpVersion 8.1 behave as before
Assert::exception() and Assert::error() check the message also when it is &apos;&apos; or &apos;0&apos;; to skip the message check, pass null
JUnit report counts failed tests in the failures attribute instead of errors; update your CI if it reads only errors
With --stop-on-fail and parallel jobs, running tests are finished before the runner exits, and Ctrl+C terminates them
Environment::lock() on Windows leaves the test its full time limit after waiting for the lock
HttpAssert with follow: true takes headers from the final response only
Code coverage: fixes in the HTML report and Clover metrics, the summary line no longer mixes into TAP or JUnit output on stdout, and tester exits with code 1 when the requested report cannot be generated

🛡️ Robustness

Fixes in edge cases of Assert::match() masks (UTF-8, %f%), FileMock (append, rb+, touch()), DomQuery selectors on PHP &lt; 8.4, Dumper with references and the JUnit report with invalid UTF-8 in the output
@multiple with an invalid value and Helpers::purge() on a path resolving to the root directory are reported as errors
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>TestCase::run()</strong> runs every test method even after one fails, so a single run shows you all failures at once: results first, details of each failure after them (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4459033444" data-permission-text="Title is private" data-url="https://github.com/nette/tester/issues/469" data-hovercard-type="issue" data-hovercard-url="/nette/tester/issues/469/hovercard" href="https://github.com/nette/tester/issues/469">#469</a>)</li>
<li>Stack traces show call arguments, so you see right away which call failed: <code>redirect('https://…', 302)</code> instead of a bare <code>redirect()</code></li>
<li>PHP 8.6 support</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>@phpVersion</code> handles the boundary versions correctly: <code>@phpVersion 8.4.3</code> runs on PHP 8.4.3 and <code>&lt; 8.0</code> no longer runs on 8.0; common forms like <code>@phpVersion 8.1</code> behave as before</li>
<li><strong>Assert::exception()</strong> and <strong>Assert::error()</strong> check the message also when it is <code>''</code> or <code>'0'</code>; to skip the message check, pass <code>null</code></li>
<li>JUnit report counts failed tests in the <code>failures</code> attribute instead of <code>errors</code>; update your CI if it reads only <code>errors</code></li>
<li>With <code>--stop-on-fail</code> and parallel jobs, running tests are finished before the runner exits, and Ctrl+C terminates them</li>
<li><strong>Environment::lock()</strong> on Windows leaves the test its full time limit after waiting for the lock</li>
<li><strong>HttpAssert</strong> with <code>follow: true</code> takes headers from the final response only</li>
<li>Code coverage: fixes in the HTML report and Clover metrics, the summary line no longer mixes into TAP or JUnit output on stdout, and <code>tester</code> exits with code 1 when the requested report cannot be generated</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Fixes in edge cases of <strong>Assert::match()</strong> masks (UTF-8, <code>%f%</code>), <strong>FileMock</strong> (append, <code>rb+</code>, <code>touch()</code>), <strong>DomQuery</strong> selectors on PHP &lt; 8.4, <strong>Dumper</strong> with references and the JUnit report with invalid UTF-8 in the output</li>
<li><code>@multiple</code> with an invalid value and <strong>Helpers::purge()</strong> on a path resolving to the root directory are reported as errors</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 13 Sep 2026 00:22:52 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tester/releases/tag/v2.6.2</guid>
	</item>
	<item>
		<title>Http v3.4.1</title>
		<link>https://github.com/nette/http/releases/tag/v3.4.1</link>
		<description>💥 Breaking Changes

Behind a trusted proxy, the DI configuration now honors only the X-Forwarded-* headers by default, so a Forwarded header sent by the client cannot spoof the address or host. If your proxy sets Forwarded, configure http: proxyHeaders: forwarded (or both)
getRemoteAddress() returns null when the forwarded client value is not a valid IP address (an obfuscated identifier or a broken chain)

✨ New Features

setBaseUrl() and the http: baseUrl option give CLI scripts (cron, tasks, MCP servers) a real request URL, so %baseUrl%, LinkGenerator, $baseUrl in templates and assets work outside the web server too. It applies only when no host can be detected, so web requests are unaffected
The http: proxyHeaders option (both|xForwarded|forwarded|none) and the new flags of RequestFactory::setProxy() choose which forwarding headers your proxy is trusted for

🐛 Bug Fixes

With multiple proxies, the client address is taken from the rightmost hop after stripping the trusted proxies, and the scheme and host come from the same hop of the Forwarded header
Response::setCookie() treats an explicitly empty $path or $domain as given (the root path or a host-only cookie); only null falls back to the configured defaults
</description>
		<content:encoded><![CDATA[
		<h2>💥 Breaking Changes</h2>
<ul>
<li>Behind a trusted proxy, the DI configuration now honors only the <code>X-Forwarded-*</code> headers by default, so a <code>Forwarded</code> header sent by the client cannot spoof the address or host. If your proxy sets <code>Forwarded</code>, configure <code>http: proxyHeaders: forwarded</code> (or <code>both</code>)</li>
<li><strong>getRemoteAddress()</strong> returns <code>null</code> when the forwarded client value is not a valid IP address (an obfuscated identifier or a broken chain)</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>setBaseUrl()</strong> and the <code>http: baseUrl</code> option give CLI scripts (cron, tasks, MCP servers) a real request URL, so <code>%baseUrl%</code>, LinkGenerator, <code>$baseUrl</code> in templates and assets work outside the web server too. It applies only when no host can be detected, so web requests are unaffected</li>
<li>The <code>http: proxyHeaders</code> option (<code>both|xForwarded|forwarded|none</code>) and the new flags of <strong>RequestFactory::setProxy()</strong> choose which forwarding headers your proxy is trusted for</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>With multiple proxies, the client address is taken from the rightmost hop after stripping the trusted proxies, and the scheme and host come from the same hop of the <code>Forwarded</code> header</li>
<li><strong>Response::setCookie()</strong> treats an explicitly empty <code>$path</code> or <code>$domain</code> as given (the root path or a host-only cookie); only <code>null</code> falls back to the configured defaults</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 27 Aug 2026 04:25:18 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/http/releases/tag/v3.4.1</guid>
	</item>
	<item>
		<title>Di v3.2.7</title>
		<link>https://github.com/nette/di/releases/tag/v3.2.7</link>
		<description>The container stops being a black box. This release adds a first-class introspection API, a PSR-11 bridge, and – finally – containers that actually reload themselves in long-running processes instead of silently serving a stale build forever. A handful of quiet misconfigurations were also promoted to loud errors.
✨ New Features

Containers now reload themselves in long-running processes. Until now, auto-rebuild only ever helped the next request: PHP cannot redeclare a class that is already loaded, so a queue worker, a dev server, a CLI tool or an MCP server kept serving the very first compiled container for the rest of its life, no matter how many times the configs changed and the file on disk was regenerated. With auto-rebuild on, ContainerLoader now gives every build a fresh class name (Container_&lt;key&gt;_&lt;hash&gt;) and, on every load(), checks the compiled file&apos;s content rather than merely whether it has just been regenerated, so a rebuild done by another process over the same cache (a web request while your worker runs) is picked up as well. A process simply gets a new container instance whenever its configuration changed, with no restart. Without auto-rebuild nothing changes: production still compiles once and never looks back.
New Container::getServiceDescriptors() – a read-only snapshot of every registered service (name, type, autowiring, tags, aliases, and the instance if it exists), in definition order, without instantiating anything. Tools that until now read the container&apos;s private properties through Closure::bind() and scanned createService* methods by reflection can drop the tricks; the Tracy panel already has.
New Nette\Bridges\DIPsr\PsrContainer – wrap your container and hand it to any library that speaks PSR-11. get() resolves both service names and autowired types, with ambiguity reported rather than guessed.
A service produced by a factory can autowire itself in its own setup, so @self and self-typed arguments work there like anywhere else.

🐛 Bug Fixes

Windows users: writing the compiled container no longer fails intermittently with &quot;Access is denied&quot; when antivirus or an opcache handle holds the target file for a moment – the rename is briefly retried, and the opcache handle is dropped first. Other platforms behave exactly as before.
addService() refuses a name already taken by a factory, matching the existing behavior for instances. The counterpart: removeService() now removes factories too, so a name freed by removeService() is genuinely free.

⚡ Performance

Registering a definition no longer scans every existing definition to check for a case-insensitive name clash; an index does it in constant time. Containers with thousands of services notice.
</description>
		<content:encoded><![CDATA[
		<p>The container stops being a black box. This release adds a first-class introspection API, a PSR-11 bridge, and – finally – containers that actually reload themselves in long-running processes instead of silently serving a stale build forever. A handful of quiet misconfigurations were also promoted to loud errors.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>Containers now reload themselves in long-running processes.</strong> Until now, auto-rebuild only ever helped the <em>next</em> request: PHP cannot redeclare a class that is already loaded, so a queue worker, a dev server, a CLI tool or an MCP server kept serving the very first compiled container for the rest of its life, no matter how many times the configs changed and the file on disk was regenerated. With auto-rebuild on, <code>ContainerLoader</code> now gives every build a fresh class name (<code>Container_&lt;key&gt;_&lt;hash&gt;</code>) and, on every <code>load()</code>, checks the compiled file's content rather than merely whether it has just been regenerated, so a rebuild done by another process over the same cache (a web request while your worker runs) is picked up as well. A process simply gets a new container instance whenever its configuration changed, with no restart. Without auto-rebuild nothing changes: production still compiles once and never looks back.</li>
<li><strong>New <code>Container::getServiceDescriptors()</code></strong> – a read-only snapshot of every registered service (name, type, autowiring, tags, aliases, and the instance if it exists), in definition order, without instantiating anything. Tools that until now read the container's private properties through <code>Closure::bind()</code> and scanned <code>createService*</code> methods by reflection can drop the tricks; the Tracy panel already has.</li>
<li><strong>New <code>Nette\Bridges\DIPsr\PsrContainer</code></strong> – wrap your container and hand it to any library that speaks PSR-11. <code>get()</code> resolves both service names and autowired types, with ambiguity reported rather than guessed.</li>
<li><strong>A service produced by a factory can autowire itself in its own <code>setup</code></strong>, so <code>@self</code> and self-typed arguments work there like anywhere else.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>Windows users: writing the compiled container no longer fails intermittently with "Access is denied" when antivirus or an opcache handle holds the target file for a moment – the rename is briefly retried, and the opcache handle is dropped first. Other platforms behave exactly as before.</li>
<li><code>addService()</code> refuses a name already taken by a factory, matching the existing behavior for instances. The counterpart: <strong><code>removeService()</code> now removes factories too</strong>, so a name freed by <code>removeService()</code> is genuinely free.</li>
</ul>
<h2>⚡ Performance</h2>
<ul>
<li>Registering a definition no longer scans every existing definition to check for a case-insensitive name clash; an index does it in constant time. Containers with thousands of services notice.</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 27 Aug 2026 01:17:30 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/di/releases/tag/v3.2.7</guid>
	</item>
	<item>
		<title>Tracy v2.12.1</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.12.1</link>
		<description>✨ New Features

Dumper understands modern PHP – virtual hooked properties are shown as {virtual}, WeakReference shows its target, PHP 8.5 Uri\Rfc3986\Uri and Uri\WhatWg\Url expand into their components, closures show the class of the bound $this, and lazy objects reveal their eagerly initialized properties
X-Tracy-Agent header – curl, HTTP clients and CI jobs can ask for markdown output with a single request header, and a non-HTML response then carries the markdown BlueScreen right in its body

🐛 Bug Fixes

The Bar&apos;s fetch() wrapper keeps the options argument and leaves the caller&apos;s Request untouched
editor: false in the Nette configuration disables editor links
Dumper::$keysToHide and the scrubber also apply to properties coming from __debugInfo() and custom object exporters, and dump() with return: true respects $keysToHide as well
cURL handles are dumped with their details again
Toggle links can be activated from the keyboard
Email notifications are throttled reliably under concurrent requests, a failed sending is retried with the next error, and an invalid $emailSnooze throws an exception
TracyToPsrLoggerAdapter logs an exception only once when the message adds nothing to it, and accepts Stringable messages

🛡️ Robustness

The session file storage is tighter: files are created with mode 0600, stored data is unserialized without objects, the cookie gets SameSite=Lax and secure on HTTPS, and concurrent garbage collection runs quietly
The Bar and dumps initialize correctly even with a corrupt localStorage entry or a broken dump payload on the page
Smaller edge cases: BlueScreen does not autoload class names found in an exception message, the fallback error output is HTML-escaped, a repeated DeferredContent::enable() is harmless, and custom Dumper exposers are picked deterministically
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Dumper</strong> understands modern PHP – virtual hooked properties are shown as <code>{virtual}</code>, <code>WeakReference</code> shows its target, PHP 8.5 <code>Uri\Rfc3986\Uri</code> and <code>Uri\WhatWg\Url</code> expand into their components, closures show the class of the bound <code>$this</code>, and lazy objects reveal their eagerly initialized properties</li>
<li><strong>X-Tracy-Agent</strong> header – curl, HTTP clients and CI jobs can ask for markdown output with a single request header, and a non-HTML response then carries the markdown BlueScreen right in its body</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>The Bar's <code>fetch()</code> wrapper keeps the options argument and leaves the caller's <code>Request</code> untouched</li>
<li><code>editor: false</code> in the Nette configuration disables editor links</li>
<li><code>Dumper::$keysToHide</code> and the scrubber also apply to properties coming from <code>__debugInfo()</code> and custom object exporters, and <code>dump()</code> with <code>return: true</code> respects <code>$keysToHide</code> as well</li>
<li>cURL handles are dumped with their details again</li>
<li>Toggle links can be activated from the keyboard</li>
<li>Email notifications are throttled reliably under concurrent requests, a failed sending is retried with the next error, and an invalid <code>$emailSnooze</code> throws an exception</li>
<li><code>TracyToPsrLoggerAdapter</code> logs an exception only once when the message adds nothing to it, and accepts <code>Stringable</code> messages</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>The session file storage is tighter: files are created with mode 0600, stored data is unserialized without objects, the cookie gets <code>SameSite=Lax</code> and <code>secure</code> on HTTPS, and concurrent garbage collection runs quietly</li>
<li>The Bar and dumps initialize correctly even with a corrupt <code>localStorage</code> entry or a broken dump payload on the page</li>
<li>Smaller edge cases: BlueScreen does not autoload class names found in an exception message, the fallback error output is HTML-escaped, a repeated <code>DeferredContent::enable()</code> is harmless, and custom Dumper exposers are picked deterministically</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 18 Aug 2026 11:06:27 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.12.1</guid>
	</item>
	<item>
		<title>Robot Loader v4.1.3</title>
		<link>https://github.com/nette/robot-loader/releases/tag/v4.1.3</link>
		<description>
setCacheDirectory() replaces setTempDirectory(), matching the naming used in Latte. The old method still works as a deprecated alias, so there is no rush to change anything.
Writing the cache on Windows no longer fails randomly with &quot;Access is denied&quot;. An antivirus scanning the freshly written file could hold it open just long enough to break the rename(); the write is now retried briefly before giving up. Other platforms behave exactly as before.
When the cache file cannot be written, the exception now tells you why instead of just naming the file.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>setCacheDirectory()</strong> replaces <code>setTempDirectory()</code>, matching the naming used in Latte. The old method still works as a deprecated alias, so there is no rush to change anything.</li>
<li>Writing the cache on Windows no longer fails randomly with "Access is denied". An antivirus scanning the freshly written file could hold it open just long enough to break the <code>rename()</code>; the write is now retried briefly before giving up. Other platforms behave exactly as before.</li>
<li>When the cache file cannot be written, the exception now tells you <em>why</em> instead of just naming the file.</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 18 Aug 2026 10:26:19 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/robot-loader/releases/tag/v4.1.3</guid>
	</item>
	<item>
		<title>Mail v4.2.1</title>
		<link>https://github.com/nette/mail/releases/tag/v4.2.1</link>
		<description>🐛 Bug Fixes

Display names are no longer quoted when they don&apos;t need to be (#107). Since 4.2.0 any name outside plain ASCII – so every name with diacritics – got wrapped in a quoted-string before MIME encoding, which buried the quotes inside the base64 payload and decoded them as part of the name: Objednávky domena.cz arrived as &quot;Objednávky domena.cz&quot;. Quoting is now reserved for characters that could genuinely restructure an address list (, ; : &lt; &gt; @ &quot; \), so Kdo uteče, obědvá keeps its quotes and the DKIM fix from #102 stands, while ordinary accented names go out clean.
</description>
		<content:encoded><![CDATA[
		<h2>🐛 Bug Fixes</h2>
<ul>
<li>Display names are no longer quoted when they don't need to be (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5178182263" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/107" data-hovercard-type="pull_request" data-hovercard-url="/nette/mail/pull/107/hovercard" href="https://github.com/nette/mail/pull/107">#107</a>). Since 4.2.0 any name outside plain ASCII – so every name with diacritics – got wrapped in a <code>quoted-string</code> <em>before</em> MIME encoding, which buried the quotes inside the base64 payload and decoded them as part of the name: <code>Objednávky domena.cz</code> arrived as <code>"Objednávky domena.cz"</code>. Quoting is now reserved for characters that could genuinely restructure an address list (<code>,</code> <code>;</code> <code>:</code> <code>&lt;</code> <code>&gt;</code> <code>@</code> <code>"</code> <code>\</code>), so <code>Kdo uteče, obědvá</code> keeps its quotes and the DKIM fix from <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2578128385" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/102" data-hovercard-type="pull_request" data-hovercard-url="/nette/mail/pull/102/hovercard" href="https://github.com/nette/mail/pull/102">#102</a> stands, while ordinary accented names go out clean.</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 18 Aug 2026 10:12:09 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.2.1</guid>
	</item>
	<item>
		<title>Schema v1.3.6</title>
		<link>https://github.com/nette/schema/releases/tag/v1.3.6</link>
		<description>A maintenance release: castTo() learns backed enums, plus a few fixes around nullable arrays, deprecated structures and anyOf().
✨ New Features

castTo() accepts a backed enum: Expect::string()-&gt;castTo(Status::class) turns the value into the enum case, and a value matching no case is a validation error listing the allowed ones

🐛 Bug Fixes

null for a nullable() array stays null instead of turning into []
A deprecated nested structure warns only when it is actually present in the input
Dynamic parameters inside anyOf() are validated by DI again, and skipDefaults is honored there

🛡️ Robustness

A cast to a class that cannot be constructed reports which class it was
Items with invalid keys no longer overwrite each other, unknown %placeholders% in messages stay intact, and getWarnings() works before the first process()
</description>
		<content:encoded><![CDATA[
		<p>A maintenance release: <code>castTo()</code> learns backed enums, plus a few fixes around nullable arrays, deprecated structures and <code>anyOf()</code>.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>castTo()</strong> accepts a backed enum: <code>Expect::string()-&gt;castTo(Status::class)</code> turns the value into the enum case, and a value matching no case is a validation error listing the allowed ones</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>null</code> for a <code>nullable()</code> array stays <code>null</code> instead of turning into <code>[]</code></li>
<li>A deprecated nested structure warns only when it is actually present in the input</li>
<li>Dynamic parameters inside <code>anyOf()</code> are validated by DI again, and <code>skipDefaults</code> is honored there</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>A cast to a class that cannot be constructed reports which class it was</li>
<li>Items with invalid keys no longer overwrite each other, unknown <code>%placeholders%</code> in messages stay intact, and <code>getWarnings()</code> works before the first <code>process()</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 17 Aug 2026 18:17:51 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/schema/releases/tag/v1.3.6</guid>
	</item>
	<item>
		<title>Routing v3.1.4</title>
		<link>https://github.com/nette/routing/releases/tag/v3.1.4</link>
		<description>
Double quotes in URL path segments are now percent-encoded as RFC 3986 requires. Previously an unencoded &quot; in a generated URL could break out of an HTML attribute in output contexts that are not HTML-escaped.
Host wildcards (%tld%, %domain%, %sld%) no longer mangle IP addresses: IPv6 hosts like [::1] and the address 0.0.0.0 were mistakenly split on dots as if they were domain names. Routes with host masks now work correctly when the site is accessed via an IP address.
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Double quotes in URL path segments are now percent-encoded as RFC 3986 requires. Previously an unencoded <code>"</code> in a generated URL could break out of an HTML attribute in output contexts that are not HTML-escaped.</li>
<li>Host wildcards (<code>%tld%</code>, <code>%domain%</code>, <code>%sld%</code>) no longer mangle IP addresses: IPv6 hosts like <code>[::1]</code> and the address <code>0.0.0.0</code> were mistakenly split on dots as if they were domain names. Routes with host masks now work correctly when the site is accessed via an IP address.</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 09 Aug 2026 14:03:45 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/routing/releases/tag/v3.1.4</guid>
	</item>
	<item>
		<title>Mail v4.1.3</title>
		<link>https://github.com/nette/mail/releases/tag/untagged-eba1b214f5c37cb81cd9</link>
		<description>This release teaches SmtpMailer to speak OAuth, DkimSigner to sign with Ed25519, and CssInliner to resolve styles the way a browser does. Add a DKIM security fix and the deliverability headers Gmail and Yahoo now demand, and there is a good reason to upgrade even if you never hit any of the fixed bugs.
🔒 Security

DkimSigner no longer emits the l= body-length tag. With it, anyone could append arbitrary content to a signed message without invalidating the signature.

✨ New Features

SmtpMailer::setAccessToken() – authenticates with an OAuth 2.0 access token (XOAUTH2), which Gmail and Microsoft 365 require now that they are retiring passwords for SMTP. Pass the token as a string, or as a callback that is called on each connection so an expiring token gets refreshed.
Message::setUnsubscribe() – emits the pair of one-click unsubscribe headers (RFC 8058) that Gmail and Yahoo require from bulk senders. Getting the two headers to agree is exactly the kind of detail that is easy to get wrong by hand; the headers are also DKIM-signed, so the unsubscribe target cannot be swapped in transit.
DkimSigner signs with Ed25519 keys (RFC 8463). The algorithm is detected from the key itself, so no new argument is needed. New header oversigning (opt-in via $oversignHeaders) makes appending a second From: header break the signature.
FileMailer – a mailer that writes each message to an .eml file instead of sending it; ideal for development and testing.
Addresses with internationalized domains – jan@příklad.cz – are converted to punycode automatically, so they work with ordinary SMTP servers instead of failing with a puzzling server error.

🐛 Bug Fixes

CssInliner resolves competing declarations by the real CSS cascade – !important, inline styles, selector specificity, source order – instead of letting the last rule win. Inlined emails now look like the page the stylesheet was written for, and each property is written out once, with the winning value.
CssInliner no longer turns width: auto or calc(...) into width=&quot;0&quot; (which collapsed the cell in Outlook), and treats property names case-insensitively, as CSS does.
Header names are case-insensitive per RFC 5322: getHeader(&apos;from&apos;) finds the From header, setHeader(&apos;SUBJECT&apos;) replaces the existing Subject instead of adding a second one, and DKIM signing matches headers whatever their spelling.
SmtpMailer got a robustness overhaul: a persistent connection dropped by an idle server is detected and re-established instead of failing every send from then on; large messages are no longer silently truncated when the socket buffer fills up; the read timeout holds even against a server that never stops talking; and authentication picks only from mechanisms the server actually offers, including the legacy AUTH= advertisement.
SmtpMailer STARTTLS accepts only TLS 1.2 and 1.3, reports the actual handshake failure reason instead of a bare &quot;Unable to connect&quot;, and defaults to the submission port 587.
FallbackMailer no longer keeps retrying a mailer whose failure is permanent, like rejected credentials – retrying cannot fix those.
DkimSigner relaxed canonicalization collapses every whitespace sequence, including tabs, so signatures on such headers verify everywhere.
</description>
		<content:encoded><![CDATA[
		<p>This release teaches SmtpMailer to speak OAuth, DkimSigner to sign with Ed25519, and CssInliner to resolve styles the way a browser does. Add a DKIM security fix and the deliverability headers Gmail and Yahoo now demand, and there is a good reason to upgrade even if you never hit any of the fixed bugs.</p>
<h2>🔒 Security</h2>
<ul>
<li><strong>DkimSigner</strong> no longer emits the <code>l=</code> body-length tag. With it, anyone could append arbitrary content to a signed message without invalidating the signature.</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>SmtpMailer::setAccessToken()</strong> – authenticates with an OAuth 2.0 access token (XOAUTH2), which Gmail and Microsoft 365 require now that they are retiring passwords for SMTP. Pass the token as a string, or as a callback that is called on each connection so an expiring token gets refreshed.</li>
<li><strong>Message::setUnsubscribe()</strong> – emits the pair of one-click unsubscribe headers (RFC 8058) that Gmail and Yahoo require from bulk senders. Getting the two headers to agree is exactly the kind of detail that is easy to get wrong by hand; the headers are also DKIM-signed, so the unsubscribe target cannot be swapped in transit.</li>
<li><strong>DkimSigner</strong> signs with Ed25519 keys (RFC 8463). The algorithm is detected from the key itself, so no new argument is needed. New header oversigning (opt-in via <code>$oversignHeaders</code>) makes appending a second <code>From:</code> header break the signature.</li>
<li><strong>FileMailer</strong> – a mailer that writes each message to an <code>.eml</code> file instead of sending it; ideal for development and testing.</li>
<li>Addresses with internationalized domains – jan@příklad.cz – are converted to punycode automatically, so they work with ordinary SMTP servers instead of failing with a puzzling server error.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>CssInliner</strong> resolves competing declarations by the real CSS cascade – <code>!important</code>, inline styles, selector specificity, source order – instead of letting the last rule win. Inlined emails now look like the page the stylesheet was written for, and each property is written out once, with the winning value.</li>
<li><strong>CssInliner</strong> no longer turns <code>width: auto</code> or <code>calc(...)</code> into <code>width="0"</code> (which collapsed the cell in Outlook), and treats property names case-insensitively, as CSS does.</li>
<li>Header names are case-insensitive per RFC 5322: <code>getHeader('from')</code> finds the <code>From</code> header, <code>setHeader('SUBJECT')</code> replaces the existing Subject instead of adding a second one, and DKIM signing matches headers whatever their spelling.</li>
<li><strong>SmtpMailer</strong> got a robustness overhaul: a persistent connection dropped by an idle server is detected and re-established instead of failing every send from then on; large messages are no longer silently truncated when the socket buffer fills up; the read timeout holds even against a server that never stops talking; and authentication picks only from mechanisms the server actually offers, including the legacy <code>AUTH=</code> advertisement.</li>
<li><strong>SmtpMailer</strong> STARTTLS accepts only TLS 1.2 and 1.3, reports the actual handshake failure reason instead of a bare "Unable to connect", and defaults to the submission port 587.</li>
<li><strong>FallbackMailer</strong> no longer keeps retrying a mailer whose failure is permanent, like rejected credentials – retrying cannot fix those.</li>
<li><strong>DkimSigner</strong> relaxed canonicalization collapses every whitespace sequence, including tabs, so signatures on such headers verify everywhere.</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 27 Jul 2026 15:39:36 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/untagged-eba1b214f5c37cb81cd9</guid>
	</item>
	<item>
		<title>Mail v4.1.3</title>
		<link>https://github.com/nette/mail/releases/tag/untagged-d4d1d6c099344612f57a</link>
		<description>This release teaches SmtpMailer to speak OAuth, DkimSigner to sign with Ed25519, and CssInliner to resolve styles the way a browser does. Add a DKIM security fix and the deliverability headers Gmail and Yahoo now demand, and there is a good reason to upgrade even if you never hit any of the fixed bugs.
🔒 Security

DkimSigner no longer emits the l= body-length tag. With it, anyone could append arbitrary content to a signed message without invalidating the signature.

✨ New Features

SmtpMailer::setAccessToken() – authenticates with an OAuth 2.0 access token (XOAUTH2), which Gmail and Microsoft 365 require now that they are retiring passwords for SMTP. Pass the token as a string, or as a callback that is called on each connection so an expiring token gets refreshed.
Message::setUnsubscribe() – emits the pair of one-click unsubscribe headers (RFC 8058) that Gmail and Yahoo require from bulk senders. Getting the two headers to agree is exactly the kind of detail that is easy to get wrong by hand; the headers are also DKIM-signed, so the unsubscribe target cannot be swapped in transit.
DkimSigner signs with Ed25519 keys (RFC 8463). The algorithm is detected from the key itself, so no new argument is needed. New header oversigning (opt-in via $oversignHeaders) makes appending a second From: header break the signature.
FileMailer – a mailer that writes each message to an .eml file instead of sending it; ideal for development and testing.
Addresses with internationalized domains – jan@příklad.cz – are converted to punycode automatically, so they work with ordinary SMTP servers instead of failing with a puzzling server error.

🐛 Bug Fixes

CssInliner resolves competing declarations by the real CSS cascade – !important, inline styles, selector specificity, source order – instead of letting the last rule win. Inlined emails now look like the page the stylesheet was written for, and each property is written out once, with the winning value.
CssInliner no longer turns width: auto or calc(...) into width=&quot;0&quot; (which collapsed the cell in Outlook), and treats property names case-insensitively, as CSS does.
Header names are case-insensitive per RFC 5322: getHeader(&apos;from&apos;) finds the From header, setHeader(&apos;SUBJECT&apos;) replaces the existing Subject instead of adding a second one, and DKIM signing matches headers whatever their spelling.
SmtpMailer got a robustness overhaul: a persistent connection dropped by an idle server is detected and re-established instead of failing every send from then on; large messages are no longer silently truncated when the socket buffer fills up; the read timeout holds even against a server that never stops talking; and authentication picks only from mechanisms the server actually offers, including the legacy AUTH= advertisement.
SmtpMailer STARTTLS accepts only TLS 1.2 and 1.3, reports the actual handshake failure reason instead of a bare &quot;Unable to connect&quot;, and defaults to the submission port 587.
FallbackMailer no longer keeps retrying a mailer whose failure is permanent, like rejected credentials – retrying cannot fix those.
DkimSigner relaxed canonicalization collapses every whitespace sequence, including tabs, so signatures on such headers verify everywhere.
</description>
		<content:encoded><![CDATA[
		<p>This release teaches SmtpMailer to speak OAuth, DkimSigner to sign with Ed25519, and CssInliner to resolve styles the way a browser does. Add a DKIM security fix and the deliverability headers Gmail and Yahoo now demand, and there is a good reason to upgrade even if you never hit any of the fixed bugs.</p>
<h2>🔒 Security</h2>
<ul>
<li><strong>DkimSigner</strong> no longer emits the <code>l=</code> body-length tag. With it, anyone could append arbitrary content to a signed message without invalidating the signature.</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>SmtpMailer::setAccessToken()</strong> – authenticates with an OAuth 2.0 access token (XOAUTH2), which Gmail and Microsoft 365 require now that they are retiring passwords for SMTP. Pass the token as a string, or as a callback that is called on each connection so an expiring token gets refreshed.</li>
<li><strong>Message::setUnsubscribe()</strong> – emits the pair of one-click unsubscribe headers (RFC 8058) that Gmail and Yahoo require from bulk senders. Getting the two headers to agree is exactly the kind of detail that is easy to get wrong by hand; the headers are also DKIM-signed, so the unsubscribe target cannot be swapped in transit.</li>
<li><strong>DkimSigner</strong> signs with Ed25519 keys (RFC 8463). The algorithm is detected from the key itself, so no new argument is needed. New header oversigning (opt-in via <code>$oversignHeaders</code>) makes appending a second <code>From:</code> header break the signature.</li>
<li><strong>FileMailer</strong> – a mailer that writes each message to an <code>.eml</code> file instead of sending it; ideal for development and testing.</li>
<li>Addresses with internationalized domains – jan@příklad.cz – are converted to punycode automatically, so they work with ordinary SMTP servers instead of failing with a puzzling server error.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>CssInliner</strong> resolves competing declarations by the real CSS cascade – <code>!important</code>, inline styles, selector specificity, source order – instead of letting the last rule win. Inlined emails now look like the page the stylesheet was written for, and each property is written out once, with the winning value.</li>
<li><strong>CssInliner</strong> no longer turns <code>width: auto</code> or <code>calc(...)</code> into <code>width="0"</code> (which collapsed the cell in Outlook), and treats property names case-insensitively, as CSS does.</li>
<li>Header names are case-insensitive per RFC 5322: <code>getHeader('from')</code> finds the <code>From</code> header, <code>setHeader('SUBJECT')</code> replaces the existing Subject instead of adding a second one, and DKIM signing matches headers whatever their spelling.</li>
<li><strong>SmtpMailer</strong> got a robustness overhaul: a persistent connection dropped by an idle server is detected and re-established instead of failing every send from then on; large messages are no longer silently truncated when the socket buffer fills up; the read timeout holds even against a server that never stops talking; and authentication picks only from mechanisms the server actually offers, including the legacy <code>AUTH=</code> advertisement.</li>
<li><strong>SmtpMailer</strong> STARTTLS accepts only TLS 1.2 and 1.3, reports the actual handshake failure reason instead of a bare "Unable to connect", and defaults to the submission port 587.</li>
<li><strong>FallbackMailer</strong> no longer keeps retrying a mailer whose failure is permanent, like rejected credentials – retrying cannot fix those.</li>
<li><strong>DkimSigner</strong> relaxed canonicalization collapses every whitespace sequence, including tabs, so signatures on such headers verify everywhere.</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 27 Jul 2026 15:39:36 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/untagged-d4d1d6c099344612f57a</guid>
	</item>
	<item>
		<title>Latte v3.1.6</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.6</link>
		<description>A release born from a deep audit of the engine: it tightens context-sensitive escaping in two places, fixes a long list of filter and compiler edge cases, adds the |map filter and the afterRender() hook, and restores a lost optimization of includes.
💥 Breaking Changes &amp; Deprecations

{$interval|date} on a DateInterval requires an explicit format, e.g. {$interval|date: &apos;%d days&apos;}
{first}, {last} and {sep} outside {foreach} trigger a deprecation; they will be a compile error in Latte 3.2
A custom sandbox policy whose rules vary at runtime should implement getCacheSignature(), as the rules are now part of the template cache key

✨ New Features

|map – transforms every item with a callback, the natural partner of |filter: {foreach ($items|map: fn($x) =&gt; $x-&gt;name) as $name}
Extension::afterRender() – a hook that runs even when rendering ends early with {exitIf} or an exception, handy for cleanup or measurement
The Tracy panel shows the render time of each template, total and without nested templates, so you see which template really takes the time
|last, |random, |implode and |commas accept any iterable, like |first, |slice and |filter already do

🔒 Security

A &lt;script&gt; whose type has surrounding whitespace is recognized as JavaScript, as browsers do, and escaped accordingly
A template compiled under one sandbox policy is not reused from the cache under a different one
xlink:href in inline SVG is sanitized like href

🐛 Bug Fixes

{capture $x|trim} keeps captured HTML as HTML and does not escape it again
{switch} without an expression works as a switch on true: {case $cond}
A partially dynamic &lt;script type=&quot;a{$dyn}&quot;&gt; compiles and is treated as JavaScript; the empty comment {**} compiles too
|reverse and |column keep every item of an iterator with repeated keys, and |indent inserts $ and \ from its argument literally
Custom n:attributes whose name contains tag- or inner- keep their name
Tag::closestTag() matches subclasses, so extensions that subclass core nodes work with {iterateWhile}, {rollback} and {include parent}
The class names of compiled templates use a 64-bit hash instead of a 40-bit one, so two templates practically cannot end up sharing one

🛡️ Robustness

Invalid input to filters reports a clear error: malformed UTF-8 in |explode and |random, an empty pad string in |padLeft/|padRight, a zero divisor in divisibleBy()
A compile error without a cache directory is reported as CompileException pointing at the generated code, and a misbehaving tag parser used as an n:attribute gets a clear error

⚡ Performance

{include}, {extends} and {embed} no longer recompute the whole engine configuration signature each time, which also fixes createTemplate(clearCache: false) as the very first call
Rendering with a parameters object is about 2.6× faster
</description>
		<content:encoded><![CDATA[
		<p>A release born from a deep audit of the engine: it tightens context-sensitive escaping in two places, fixes a long list of filter and compiler edge cases, adds the <strong>|map</strong> filter and the <strong>afterRender()</strong> hook, and restores a lost optimization of includes.</p>
<h2>💥 Breaking Changes &amp; Deprecations</h2>
<ul>
<li><code>{$interval|date}</code> on a <code>DateInterval</code> requires an explicit format, e.g. <code>{$interval|date: '%d days'}</code></li>
<li><code>{first}</code>, <code>{last}</code> and <code>{sep}</code> outside <code>{foreach}</code> trigger a deprecation; they will be a compile error in Latte 3.2</li>
<li>A custom sandbox policy whose rules vary at runtime should implement <code>getCacheSignature()</code>, as the rules are now part of the template cache key</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>|map</strong> – transforms every item with a callback, the natural partner of <code>|filter</code>: <code>{foreach ($items|map: fn($x) =&gt; $x-&gt;name) as $name}</code></li>
<li><strong>Extension::afterRender()</strong> – a hook that runs even when rendering ends early with <code>{exitIf}</code> or an exception, handy for cleanup or measurement</li>
<li>The <strong>Tracy panel</strong> shows the render time of each template, total and without nested templates, so you see which template really takes the time</li>
<li><strong>|last</strong>, <strong>|random</strong>, <strong>|implode</strong> and <strong>|commas</strong> accept any iterable, like <code>|first</code>, <code>|slice</code> and <code>|filter</code> already do</li>
</ul>
<h2>🔒 Security</h2>
<ul>
<li>A <code>&lt;script&gt;</code> whose <code>type</code> has surrounding whitespace is recognized as JavaScript, as browsers do, and escaped accordingly</li>
<li>A template compiled under one sandbox policy is not reused from the cache under a different one</li>
<li><code>xlink:href</code> in inline SVG is sanitized like <code>href</code></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>{capture $x|trim}</code> keeps captured HTML as HTML and does not escape it again</li>
<li><code>{switch}</code> without an expression works as a switch on <code>true</code>: <code>{case $cond}</code></li>
<li>A partially dynamic <code>&lt;script type="a{$dyn}"&gt;</code> compiles and is treated as JavaScript; the empty comment <code>{**}</code> compiles too</li>
<li><code>|reverse</code> and <code>|column</code> keep every item of an iterator with repeated keys, and <code>|indent</code> inserts <code>$</code> and <code>\</code> from its argument literally</li>
<li>Custom n:attributes whose name contains <code>tag-</code> or <code>inner-</code> keep their name</li>
<li><code>Tag::closestTag()</code> matches subclasses, so extensions that subclass core nodes work with <code>{iterateWhile}</code>, <code>{rollback}</code> and <code>{include parent}</code></li>
<li>The class names of compiled templates use a 64-bit hash instead of a 40-bit one, so two templates practically cannot end up sharing one</li>
</ul>
<h2>🛡️ Robustness</h2>
<ul>
<li>Invalid input to filters reports a clear error: malformed UTF-8 in <code>|explode</code> and <code>|random</code>, an empty pad string in <code>|padLeft</code>/<code>|padRight</code>, a zero divisor in <code>divisibleBy()</code></li>
<li>A compile error without a cache directory is reported as <code>CompileException</code> pointing at the generated code, and a misbehaving tag parser used as an n:attribute gets a clear error</li>
</ul>
<h2>⚡ Performance</h2>
<ul>
<li><code>{include}</code>, <code>{extends}</code> and <code>{embed}</code> no longer recompute the whole engine configuration signature each time, which also fixes <code>createTemplate(clearCache: false)</code> as the very first call</li>
<li>Rendering with a <strong>parameters object</strong> is about 2.6× faster</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 27 Jul 2026 15:34:55 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.6</guid>
	</item>
	<item>
		<title>Latte v3.1.5</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.5</link>
		<description>Template inheritance gets more flexible: a layout can receive its own variables and {embed} takes content without a {block} wrapper. And {spaceless} now really understands HTML.
✨ New Features

{spaceless} is a new streaming minifier that understands HTML: it strips whitespace around block elements, keeps the space between words around inline tags such as &lt;a&gt; or &lt;i&gt;, and leaves &lt;pre&gt;, &lt;textarea&gt;, &lt;script&gt;, &lt;style&gt; and attribute values untouched. |spaceless and |strip use the same minifier
{layout &apos;parent.latte&apos;, title: &apos;Hello&apos;} passes variables straight to the parent template; they reach the layout only and override parameters of the same name. Works with {extends} too, and the comma before the arguments is required
Implicit default block for {embed} – content written directly inside {embed} overrides {block default} of the embedded template (#419)
|json as the last modifier of an attribute JSON-encodes its value with proper quoting: &lt;div data-config={$config|json}&gt;

🐛 Bug Fixes

{include parent} and {include this} work inside dynamically named blocks
{contentType} inside &lt;script&gt; switches the escaping context

🛠 For Extension Developers

Every node has its source extent as Node::$position and the new Node::$end; Range is a standalone start/end object again, changing the shape introduced in 3.1.4. Call FragmentNode::updateExtent() once the tree is built
NodeTraverser throws a clear LogicException when a visitor replaces or removes a child in a way its parent does not allow
</description>
		<content:encoded><![CDATA[
		<p>Template inheritance gets more flexible: a layout can receive its own variables and <code>{embed}</code> takes content without a <code>{block}</code> wrapper. And <code>{spaceless}</code> now really understands HTML.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>{spaceless}</strong> is a new streaming minifier that understands HTML: it strips whitespace around block elements, keeps the space between words around inline tags such as <code>&lt;a&gt;</code> or <code>&lt;i&gt;</code>, and leaves <code>&lt;pre&gt;</code>, <code>&lt;textarea&gt;</code>, <code>&lt;script&gt;</code>, <code>&lt;style&gt;</code> and attribute values untouched. <code>|spaceless</code> and <code>|strip</code> use the same minifier</li>
<li><strong>{layout 'parent.latte', title: 'Hello'}</strong> passes variables straight to the parent template; they reach the layout only and override parameters of the same name. Works with <code>{extends}</code> too, and the comma before the arguments is required</li>
<li><strong>Implicit default block for {embed}</strong> – content written directly inside <code>{embed}</code> overrides <code>{block default}</code> of the embedded template (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4675105687" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/419" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/419/hovercard" href="https://github.com/nette/latte/pull/419">#419</a>)</li>
<li><strong>|json</strong> as the last modifier of an attribute JSON-encodes its value with proper quoting: <code>&lt;div data-config={$config|json}&gt;</code></li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>{include parent}</code> and <code>{include this}</code> work inside dynamically named blocks</li>
<li><code>{contentType}</code> inside <code>&lt;script&gt;</code> switches the escaping context</li>
</ul>
<h2>🛠 For Extension Developers</h2>
<ul>
<li>Every node has its source extent as <code>Node::$position</code> and the new <code>Node::$end</code>; <code>Range</code> is a standalone start/end object again, changing the shape introduced in 3.1.4. Call <code>FragmentNode::updateExtent()</code> once the tree is built</li>
<li><code>NodeTraverser</code> throws a clear <code>LogicException</code> when a visitor replaces or removes a child in a way its parent does not allow</li>
</ul>
		]]></content:encoded>
		<pubDate>Sat, 25 Jul 2026 15:46:54 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.5</guid>
	</item>
	<item>
		<title>Security v3.2.6</title>
		<link>https://github.com/nette/security/releases/tag/v3.2.6</link>
		<description>✨ New Features

Hashed passwords in SimpleAuthenticator – stored passwords may now be crypt-format hashes (anything password_hash() produces) and can be freely mixed with plain-text ones. The format is detected automatically, so hashes just work in the security: users: config section with no extra option. A hash whose algorithm the PHP build doesn&apos;t know fails closed instead of being compared as plain text, and plain-text comparison is timing-safe.
Passwords::bcrypt() and Passwords::argon2id() – name the algorithm instead of juggling PASSWORD_* constants and options arrays: Passwords::bcrypt(12) or Passwords::argon2id(memoryCost: 65536). Omitted parameters keep PHP&apos;s defaults, and argon2id() fails with a clear exception on builds without Argon2 support.
ACL rules in the configuration – the new rules section lets you define permissions declaratively next to your roles and resources:
security:
    rules:
        allow:
            - [guest, article, view]
            - [registered, comment, [add, edit]]
            - [admin]
        deny:
            - [banned, comment, add]
Each rule is [role(s), resource(s), privilege(s)]; an omitted or null item means &quot;all&quot;, and a bare string grants or revokes everything for that role. Malformed rules are rejected at config time, not at runtime.

🐛 Bug Fixes

logout() no longer touches the storage when there is nothing to change, so logging out a guest doesn&apos;t needlessly regenerate the session ID or overwrite the logout reason. A stored authentication vetoed by wakeupIdentity() (a revoked token, say) is still properly cleared.
Permission::isAllowed() now saves and restores the queried role and resource, making it re-entrant and exception-safe – an assertion callback can call isAllowed() again without corrupting the results of the outer query.
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Hashed passwords in <code>SimpleAuthenticator</code></strong> – stored passwords may now be crypt-format hashes (anything <code>password_hash()</code> produces) and can be freely mixed with plain-text ones. The format is detected automatically, so hashes just work in the <code>security: users:</code> config section with no extra option. A hash whose algorithm the PHP build doesn't know fails closed instead of being compared as plain text, and plain-text comparison is timing-safe.</li>
<li><strong><code>Passwords::bcrypt()</code> and <code>Passwords::argon2id()</code></strong> – name the algorithm instead of juggling <code>PASSWORD_*</code> constants and options arrays: <code>Passwords::bcrypt(12)</code> or <code>Passwords::argon2id(memoryCost: 65536)</code>. Omitted parameters keep PHP's defaults, and <code>argon2id()</code> fails with a clear exception on builds without Argon2 support.</li>
<li><strong>ACL rules in the configuration</strong> – the new <code>rules</code> section lets you define permissions declaratively next to your roles and resources:
<div class="highlight highlight-source-neon notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="security:
    rules:
        allow:
            - [guest, article, view]
            - [registered, comment, [add, edit]]
            - [admin]
        deny:
            - [banned, comment, add]"><pre><span class="pl-ent">security</span><span class="pl-k">:</span>
    <span class="pl-ent">rules</span><span class="pl-k">:</span>
        <span class="pl-ent">allow</span><span class="pl-k">:</span>
            <span class="pl-s">- [guest</span>, <span class="pl-s">article</span>, <span class="pl-s">view</span>]
            <span class="pl-s">- [registered</span>, <span class="pl-s">comment</span>, [<span class="pl-s">add</span>, <span class="pl-s">edit</span>]]
            <span class="pl-s">- [admin</span>]
        <span class="pl-ent">deny</span><span class="pl-k">:</span>
            <span class="pl-s">- [banned</span>, <span class="pl-s">comment</span>, <span class="pl-s">add</span>]</pre></div>
Each rule is <code>[role(s), resource(s), privilege(s)]</code>; an omitted or null item means "all", and a bare string grants or revokes everything for that role. Malformed rules are rejected at config time, not at runtime.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>logout()</code> no longer touches the storage when there is nothing to change, so logging out a guest doesn't needlessly regenerate the session ID or overwrite the logout reason. A stored authentication vetoed by <code>wakeupIdentity()</code> (a revoked token, say) is still properly cleared.</li>
<li><code>Permission::isAllowed()</code> now saves and restores the queried role and resource, making it re-entrant and exception-safe – an assertion callback can call <code>isAllowed()</code> again without corrupting the results of the outer query.</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 24 Jul 2026 23:44:31 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/security/releases/tag/v3.2.6</guid>
	</item>
	<item>
		<title>Utils v4.1.5</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.5</link>
		<description>This release adds an immutable date/time class, makes file writes safer, background processes possible, and Finder masks smarter. Plus a couple of bug fixes worth picking up.
✨ New Features

DateTimeImmutable – a new immutable counterpart to Nette\Utils\DateTime. It extends PHP&apos;s \DateTimeImmutable with strict validation (invalid dates and times throw instead of being silently rolled over), convenient factories from() and fromParts(), DST-safe relative modifications, and JSON serialization.
FileSystem::writeAtomic() – writes a file atomically via a temporary file and rename, so a concurrent reader never sees it partially written or truncated. Ideal for caches and generated configs.
Process::detach() – lets a process keep running in the background after the Process object is destroyed, instead of being killed by the destructor. Output must go to a file or be discarded, since nobody reads the pipes after detaching.
Process – on Windows with PHP 8.5, captured output now flows through real pipes instead of temporary files, thanks to the fixed stream_select().
Html::fragment() and add() – create a nameless element pre-filled with children, or append children to an existing element. Unlike addHtml(), plain strings are escaped by default and nulls are skipped.
Html::text() and Html::html() – new static factories replacing fromText() and fromHtml(), which are now deprecated.
Finder – the mask now fully drives recursion: **/foo together with in() searches recursively, and the ** short form expands like in zsh, so test/** means test/**/* and **.c means **/*.c (previously such masks silently degraded to a single *).
Finder – a trailing slash in a find() mask matches directories only: find(&apos;temp/&apos;).
Finder::exclude() – now uses the same mask grammar as find(): **.txt works, ./ anchors to the search root, and a trailing /, /* or /** controls whether the directory itself, its contents, or both are excluded.
Finder – paths are no longer normalized to forward slashes; they stay in their native form, which also fixes corruption of backslashes in POSIX file names. Note: on Windows, returned paths may now contain backslashes where they used to be unified.

🐛 Bug Fixes

ArrayList::prepend() – no longer misbehaves on an empty list.
Validators::isUrl() – now rejects malformed IPv4 addresses with octets above 255, so nonsense like https://999.1.1.1 no longer passes as a valid URL.
Strings::compare() – tolerates invalid UTF-8 instead of failing when the Normalizer gives up.
Strings::length() – the fallback used when neither mbstring nor iconv is available no longer relies on the deprecated utf8_decode(), so it stays quiet on PHP 8.2+.
Finder::exclude() – exclude(&apos;subdir/&apos;) silently excluded nothing due to a greedy regex; the trailing /, /* and /** variants now work as documented.
</description>
		<content:encoded><![CDATA[
		<p>This release adds an immutable date/time class, makes file writes safer, background processes possible, and Finder masks smarter. Plus a couple of bug fixes worth picking up.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>DateTimeImmutable</strong> – a new immutable counterpart to <code>Nette\Utils\DateTime</code>. It extends PHP's <code>\DateTimeImmutable</code> with strict validation (invalid dates and times throw instead of being silently rolled over), convenient factories <code>from()</code> and <code>fromParts()</code>, DST-safe relative modifications, and JSON serialization.</li>
<li><strong>FileSystem::writeAtomic()</strong> – writes a file atomically via a temporary file and rename, so a concurrent reader never sees it partially written or truncated. Ideal for caches and generated configs.</li>
<li><strong>Process::detach()</strong> – lets a process keep running in the background after the <code>Process</code> object is destroyed, instead of being killed by the destructor. Output must go to a file or be discarded, since nobody reads the pipes after detaching.</li>
<li><strong>Process</strong> – on Windows with PHP 8.5, captured output now flows through real pipes instead of temporary files, thanks to the fixed <code>stream_select()</code>.</li>
<li><strong>Html::fragment()</strong> and <strong>add()</strong> – create a nameless element pre-filled with children, or append children to an existing element. Unlike <code>addHtml()</code>, plain strings are escaped by default and nulls are skipped.</li>
<li><strong>Html::text()</strong> and <strong>Html::html()</strong> – new static factories replacing <code>fromText()</code> and <code>fromHtml()</code>, which are now deprecated.</li>
<li><strong>Finder</strong> – the mask now fully drives recursion: <code>**/foo</code> together with <code>in()</code> searches recursively, and the <code>**</code> short form expands like in zsh, so <code>test/**</code> means <code>test/**/*</code> and <code>**.c</code> means <code>**/*.c</code> (previously such masks silently degraded to a single <code>*</code>).</li>
<li><strong>Finder</strong> – a trailing slash in a <code>find()</code> mask matches directories only: <code>find('temp/')</code>.</li>
<li><strong>Finder::exclude()</strong> – now uses the same mask grammar as <code>find()</code>: <code>**.txt</code> works, <code>./</code> anchors to the search root, and a trailing <code>/</code>, <code>/*</code> or <code>/**</code> controls whether the directory itself, its contents, or both are excluded.</li>
<li><strong>Finder</strong> – paths are no longer normalized to forward slashes; they stay in their native form, which also fixes corruption of backslashes in POSIX file names. Note: on Windows, returned paths may now contain backslashes where they used to be unified.</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>ArrayList::prepend()</strong> – no longer misbehaves on an empty list.</li>
<li><strong>Validators::isUrl()</strong> – now rejects malformed IPv4 addresses with octets above 255, so nonsense like <code>https://999.1.1.1</code> no longer passes as a valid URL.</li>
<li><strong>Strings::compare()</strong> – tolerates invalid UTF-8 instead of failing when the Normalizer gives up.</li>
<li><strong>Strings::length()</strong> – the fallback used when neither <code>mbstring</code> nor <code>iconv</code> is available no longer relies on the deprecated <code>utf8_decode()</code>, so it stays quiet on PHP 8.2+.</li>
<li><strong>Finder::exclude()</strong> – <code>exclude('subdir/')</code> silently excluded nothing due to a greedy regex; the trailing <code>/</code>, <code>/*</code> and <code>/**</code> variants now work as documented.</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 17 Jul 2026 23:09:52 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.5</guid>
	</item>
	<item>
		<title>Application v3.2.12</title>
		<link>https://github.com/nette/application/releases/tag/v3.2.12</link>
		<description>A hardening release. Crafted or malformed request parameters that used to slip through as uncaught 500s now degrade gracefully to 4xx. If your site gets probed by scanners – and it does – these three fixes turn a batch of &quot;Server Error&quot; reports into clean Bad Request / Not Found responses.

Self-links no longer crash on bad input – when a presenter builds a link to the current page (redirect(&apos;this&apos;), forward(&apos;this&apos;), isLinkCurrent(&apos;this&apos;), typically from a language switcher) while the current URL carries a parameter that doesn&apos;t fit the action&apos;s typed signature (e.g. ?id=abc for int $id), the framework raised an uncaught InvalidLinkException (HTTP 500). It now reports a proper BadRequestException (4xx) through the new InvalidRequestParameterException. Explicitly passed bad link arguments still throw InvalidLinkException, so genuine programmer mistakes stay visible.
Numeric component ids no longer trigger a TypeError – a crafted query key such as ?1-foo=bar produced a numeric component id that hit getComponent()&apos;s string type hint and threw a TypeError (HTTP 500). The id is now cast to string and the request is handled gracefully.
Routing panel survives weird parameters – a request like ?do[]=x could crash Tracy&apos;s routing panel during development. It now skips non-string presenter/signal/action values instead of throwing.
</description>
		<content:encoded><![CDATA[
		<p>A hardening release. Crafted or malformed request parameters that used to slip through as uncaught <strong>500s</strong> now degrade gracefully to <strong>4xx</strong>. If your site gets probed by scanners – and it does – these three fixes turn a batch of "Server Error" reports into clean Bad Request / Not Found responses.</p>
<ul>
<li><strong>Self-links no longer crash on bad input</strong> – when a presenter builds a link to the current page (<code>redirect('this')</code>, <code>forward('this')</code>, <code>isLinkCurrent('this')</code>, typically from a language switcher) while the current URL carries a parameter that doesn't fit the action's typed signature (e.g. <code>?id=abc</code> for <code>int $id</code>), the framework raised an uncaught <code>InvalidLinkException</code> (HTTP 500). It now reports a proper <code>BadRequestException</code> (4xx) through the new <strong><code>InvalidRequestParameterException</code></strong>. Explicitly passed bad link arguments still throw <code>InvalidLinkException</code>, so genuine programmer mistakes stay visible.</li>
<li><strong>Numeric component ids no longer trigger a TypeError</strong> – a crafted query key such as <code>?1-foo=bar</code> produced a numeric component id that hit <code>getComponent()</code>'s <code>string</code> type hint and threw a <code>TypeError</code> (HTTP 500). The id is now cast to string and the request is handled gracefully.</li>
<li><strong>Routing panel survives weird parameters</strong> – a request like <code>?do[]=x</code> could crash Tracy's routing panel during development. It now skips non-string presenter/signal/action values instead of throwing.</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 29 Jun 2026 19:06:50 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.2.12</guid>
	</item>
	<item>
		<title>Application v3.3.0</title>
		<link>https://github.com/nette/application/releases/tag/v3.3.0</link>
		<description>Nette Application 3.3 modernizes the foundations: PHP 8.3+ and Latte 3.1, more reliable CSRF protection driven by the browser itself, and a default presenter mapping that finally matches the structure used throughout the documentation. It also clears out a pile of long-forgotten legacy. Please test the RC and report anything that breaks before the stable release.
💥 Breaking Changes

PHP 8.3 – 8.5 and Latte 3.1 are now required
More reliable CSRF protection – same-origin is now verified via the browser&apos;s Sec-Fetch-Site header instead of a SameSite cookie.
Default presenter mapping is now App\Presentation\*\**Presenter
Application::processRequest() returns a Response instead of sending it itself (#350) – sending is handled by run(). This enables long-running runtimes (RoadRunner, FrankenPHP) and PSR integration.
Presenter::getRequest() throws instead of returning null when the presenter isn&apos;t running yet
LatteFactory::create() now takes ?Control – update any custom LatteFactory implementation to the new create(?Control $control = null) signature.
Removed {ifCurrent} – use {if isLinkCurrent(&apos;...&apos;)}.
Removed compatibility with old class names such as PresenterComponent and IRouter.

⚠️ Deprecations
Mostly very old curiosities that few people knew existed – they still work but now emit a deprecation notice:

@annotations → PHP attributes: @persistent → #[Persistent], @crossOrigin → #[Requires(sameOrigin: false)], @deprecated → #[Deprecated].
Array access on RouteList – $router[] = new Route(...) and friends are replaced by $router-&gt;addRoute(...) / getRouters().
Query string in a link destination – link(&apos;Product:detail?id=1&apos;) should pass arguments instead: link(&apos;Product:detail&apos;, [&apos;id&apos; =&gt; 1]).
Component::getParameter() second $default argument – use the ?? operator instead.
Some magic properties ($presenter-&gt;view, $layout, $request, $session…) – use the getters.

✨ New Features

Set the URL fragment straight from arguments – link(&apos;Product:detail&apos;, [&apos;#&apos; =&gt; &apos;reviews&apos;]) produces ...#reviews. The value is URL-encoded, must be scalar, and isn&apos;t passed on as a request parameter.
New Presenter::completeTemplate() – a protected method extracted from sendTemplate() that you can override to inject shared variables or set the template file before rendering.
</description>
		<content:encoded><![CDATA[
		<p>Nette Application 3.3 modernizes the foundations: PHP 8.3+ and Latte 3.1, more reliable CSRF protection driven by the browser itself, and a default presenter mapping that finally matches the structure used throughout the documentation. It also clears out a pile of long-forgotten legacy. Please test the RC and report anything that breaks before the stable release.</p>
<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>PHP 8.3 – 8.5 and Latte 3.1 are now required</strong></li>
<li><strong>More reliable CSRF protection</strong> – same-origin is now verified via the browser's <code>Sec-Fetch-Site</code> header instead of a SameSite cookie.</li>
<li><strong>Default presenter mapping is now <code>App\Presentation\*\**Presenter</code></strong></li>
<li><strong><code>Application::processRequest()</code> returns a <code>Response</code></strong> instead of sending it itself (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3166208456" data-permission-text="Title is private" data-url="https://github.com/nette/application/issues/350" data-hovercard-type="pull_request" data-hovercard-url="/nette/application/pull/350/hovercard" href="https://github.com/nette/application/pull/350">#350</a>) – sending is handled by <code>run()</code>. This enables long-running runtimes (RoadRunner, FrankenPHP) and PSR integration.</li>
<li><strong><code>Presenter::getRequest()</code> throws instead of returning <code>null</code></strong> when the presenter isn't running yet</li>
<li><strong><code>LatteFactory::create()</code> now takes <code>?Control</code></strong> – update any custom <code>LatteFactory</code> implementation to the new <code>create(?Control $control = null)</code> signature.</li>
<li><strong>Removed <code>{ifCurrent}</code></strong> – use <code>{if isLinkCurrent('...')}</code>.</li>
<li><strong>Removed compatibility with old class names</strong> such as <code>PresenterComponent</code> and <code>IRouter</code>.</li>
</ul>
<h2><g-emoji class="g-emoji" alias="warning">⚠️</g-emoji> Deprecations</h2>
<p>Mostly very old curiosities that few people knew existed – they still work but now emit a deprecation notice:</p>
<ul>
<li><strong><code>@annotations</code> → PHP attributes</strong>: <code>@persistent</code> → <code>#[Persistent]</code>, <code>@crossOrigin</code> → <code>#[Requires(sameOrigin: false)]</code>, <code>@deprecated</code> → <code>#[Deprecated]</code>.</li>
<li><strong>Array access on <code>RouteList</code></strong> – <code>$router[] = new Route(...)</code> and friends are replaced by <code>$router-&gt;addRoute(...)</code> / <code>getRouters()</code>.</li>
<li><strong>Query string in a link destination</strong> – <code>link('Product:detail?id=1')</code> should pass arguments instead: <code>link('Product:detail', ['id' =&gt; 1])</code>.</li>
<li><strong><code>Component::getParameter()</code> second <code>$default</code> argument</strong> – use the <code>??</code> operator instead.</li>
<li><strong>Some magic properties</strong> (<code>$presenter-&gt;view</code>, <code>$layout</code>, <code>$request</code>, <code>$session</code>…) – use the getters.</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>Set the URL fragment straight from arguments</strong> – <code>link('Product:detail', ['#' =&gt; 'reviews'])</code> produces <code>...#reviews</code>. The value is URL-encoded, must be scalar, and isn't passed on as a request parameter.</li>
<li><strong>New <code>Presenter::completeTemplate()</code></strong> – a <code>protected</code> method extracted from <code>sendTemplate()</code> that you can override to inject shared variables or set the template file before rendering.</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 24 Jun 2026 18:26:19 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.3.0</guid>
	</item>
	<item>
		<title>Forms v3.3.0</title>
		<link>https://github.com/nette/forms/releases/tag/v3.3.0</link>
		<description>The headline of 3.3 is CSRF protection that the browser handles for you – no token, no cookie, no server-side state, and it holds even against XSS. On top of that, the confusing {formContext} / {formContainer} pair collapses into a single {form scope}, you can finally nest forms with {form detached}, and a round of housekeeping clears out long-deprecated APIs. Please test and report anything that breaks for you.

PHP 8.3+ and Latte 3.1.4+ are now required.

💥 Breaking Changes

CSRF is now strictly same-origin. Forms validate the Sec-Fetch-Site header instead of the old SameSite cookie. The previous mechanism trusted submissions from any subdomain of the same site; the new one demands an exact origin match (scheme + host + port).
setValues() / setDefaults() now expect iterable|stdClass.
RadioList / CheckboxList: getControlPart() and getLabelPart() throw on an invalid item key instead of silently returning a nonsensical result.
Removed long-deprecated APIs:** DataClassGenerator, LatteRenderer, getValues(true) (use getValues(&apos;array&apos;)), and the $default parameter of getOption() (use the ?? operator), negative validation rules

✨ New Features

{form scope name} – one tag to replace the easily-confused {formContext} and {formContainer}. It pushes the form onto the stack without emitting &lt;form&gt;, resolving the name relatively to an active form when there is one, otherwise from the top level.
{form detached name} – nest forms at last. HTML forbids nested &lt;form&gt; tags, so detached emits an empty &lt;form&gt;&lt;/form&gt; up front and links every control back to it via the HTML5 form=&quot;...&quot; attribute, no matter where they sit in the DOM.
addSubmit() accepts an $onSubmit callback – attach a click handler right when you create the button, without a separate -&gt;onClick[] =.

🗑️ Deprecations

A missing comma before {form} arguments – write {form name, attr=val} instead of {form name attr=val}, freeing keywords like scope/detached next to the name. This script adds the missing commas to your templates.
Several magic properties
</description>
		<content:encoded><![CDATA[
		<p>The headline of 3.3 is <strong>CSRF protection that the browser handles for you</strong> – no token, no cookie, no server-side state, and it holds even against XSS. On top of that, the confusing <code>{formContext}</code> / <code>{formContainer}</code> pair collapses into a single <code>{form scope}</code>, you can finally nest forms with <code>{form detached}</code>, and a round of housekeeping clears out long-deprecated APIs. Please test and report anything that breaks for you.</p>
<ul>
<li><strong>PHP 8.3+ and Latte 3.1.4+ are now required.</strong></li>
</ul>
<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>CSRF is now strictly same-origin.</strong> Forms validate the <code>Sec-Fetch-Site</code> header instead of the old SameSite cookie. The previous mechanism trusted submissions from any subdomain of the same site; the new one demands an exact origin match (scheme + host + port).</li>
<li><code>setValues()</code> / <code>setDefaults()</code> now expect <code>iterable|stdClass</code>.</li>
<li><code>RadioList</code> / <code>CheckboxList</code>: <code>getControlPart()</code> and <code>getLabelPart()</code> throw on an invalid item key instead of silently returning a nonsensical result.</li>
<li>Removed long-deprecated APIs:** <code>DataClassGenerator</code>, <code>LatteRenderer</code>, <code>getValues(true)</code> (use <code>getValues('array')</code>), and the <code>$default</code> parameter of <code>getOption()</code> (use the <code>??</code> operator), negative validation rules</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong><code>{form scope name}</code></strong> – one tag to replace the easily-confused <code>{formContext}</code> and <code>{formContainer}</code>. It pushes the form onto the stack without emitting <code>&lt;form&gt;</code>, resolving the name relatively to an active form when there is one, otherwise from the top level.</li>
<li><strong><code>{form detached name}</code></strong> – nest forms at last. HTML forbids nested <code>&lt;form&gt;</code> tags, so <code>detached</code> emits an empty <code>&lt;form&gt;&lt;/form&gt;</code> up front and links every control back to it via the HTML5 <code>form="..."</code> attribute, no matter where they sit in the DOM.</li>
<li><strong><code>addSubmit()</code> accepts an <code>$onSubmit</code> callback</strong> – attach a click handler right when you create the button, without a separate <code>-&gt;onClick[] =</code>.</li>
</ul>
<h2>🗑️ Deprecations</h2>
<ul>
<li>A missing comma before <code>{form}</code> arguments – write <code>{form name, attr=val}</code> instead of <code>{form name attr=val}</code>, freeing keywords like <code>scope</code>/<code>detached</code> next to the name. <a target=_blank rel=noopener href="https://gist.github.com/dg/ec6ee5335db26443660eb9dd367b1bf6">This script</a> adds the missing commas to your templates.</li>
<li>Several magic properties</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 24 Jun 2026 17:13:42 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/forms/releases/tag/v3.3.0</guid>
	</item>
	<item>
		<title>Component Model v4.0.0</title>
		<link>https://github.com/nette/component-model/releases/tag/v4.0.0</link>
		<description>A focused, modern major release. The component model drops legacy baggage, demands PHP 8.3+, and ships a smarter monitoring system that finally behaves predictably when listeners reshape the tree. If you&apos;ve been carrying around deprecated attached()/detached() hooks or the magic getComponents() parameters, this is your cue to clean up – the payoff is a leaner, stricter, more reliable foundation.
💥 Breaking Changes


Monitoring handlers now fire top-down (ancestor → descendant). When a subtree is attached, monitor() listeners are invoked from the outermost ancestor inward, matching the natural order of tree construction. The new implementation is robust against listeners that mutate the tree mid-flight: it re-checks validity before descending into children, deduplicates so the same listener never runs twice, and guards against reentry to prevent infinite loops. If your code relied on the old ordering, review listeners that depend on sibling or parent state.


attached() / detached() methods removed. These long-deprecated lifecycle hooks are gone. Migrate to explicit callbacks: replace overridden attached($obj) / detached($obj) with monitor($type, attached: ..., detached: ...). Calling monitor() with no handler at all now throws an InvalidStateException – at least one of attached or detached is required.


Container::getComponents() parameters removed. The method now takes no arguments and returns a plain array of immediate children (previously iterable). The old recursive flag and filter-type argument are gone – passing them throws a DeprecatedException. For recursive traversal use getComponentTree() instead. The internal RecursiveComponentIterator has been removed.


IContainer::addComponent() signature tightened. Now declared as addComponent(IComponent $component, ?string $name): static. Implementations and callers must match the new return type hint.


Nette\SmartObject dropped from Component. The component no longer pulls in the SmartObject trait, and the magic $name, $parent, and $components properties are gone. Use the explicit methods (getName(), getParent(), getComponents()) directly.


IComponent::NAME_SEPARATOR removed. Use IComponent::NameSeparator instead.


PHP 8.3 required.

</description>
		<content:encoded><![CDATA[
		<p>A focused, modern major release. The component model drops legacy baggage, demands PHP 8.3+, and ships a smarter monitoring system that finally behaves predictably when listeners reshape the tree. If you've been carrying around deprecated <code>attached()</code>/<code>detached()</code> hooks or the magic <code>getComponents()</code> parameters, this is your cue to clean up – the payoff is a leaner, stricter, more reliable foundation.</p>
<h2>💥 Breaking Changes</h2>
<ul>
<li>
<p><strong>Monitoring handlers now fire top-down (ancestor → descendant).</strong> When a subtree is attached, <code>monitor()</code> listeners are invoked from the outermost ancestor inward, matching the natural order of tree construction. The new implementation is robust against listeners that mutate the tree mid-flight: it re-checks validity before descending into children, deduplicates so the same listener never runs twice, and guards against reentry to prevent infinite loops. If your code relied on the old ordering, review listeners that depend on sibling or parent state.</p>
</li>
<li>
<p><strong><code>attached()</code> / <code>detached()</code> methods removed.</strong> These long-deprecated lifecycle hooks are gone. Migrate to explicit callbacks: replace overridden <code>attached($obj)</code> / <code>detached($obj)</code> with <code>monitor($type, attached: ..., detached: ...)</code>. Calling <code>monitor()</code> with no handler at all now throws an <code>InvalidStateException</code> – at least one of <code>attached</code> or <code>detached</code> is required.</p>
</li>
<li>
<p><strong><code>Container::getComponents()</code> parameters removed.</strong> The method now takes no arguments and returns a plain <code>array</code> of immediate children (previously <code>iterable</code>). The old recursive flag and filter-type argument are gone – passing them throws a <code>DeprecatedException</code>. For recursive traversal use <strong><code>getComponentTree()</code></strong> instead. The internal <code>RecursiveComponentIterator</code> has been removed.</p>
</li>
<li>
<p><strong><code>IContainer::addComponent()</code> signature tightened.</strong> Now declared as <code>addComponent(IComponent $component, ?string $name): static</code>. Implementations and callers must match the new return type hint.</p>
</li>
<li>
<p><strong><code>Nette\SmartObject</code> dropped from <code>Component</code>.</strong> The component no longer pulls in the <code>SmartObject</code> trait, and the magic <code>$name</code>, <code>$parent</code>, and <code>$components</code> properties are gone. Use the explicit methods (<code>getName()</code>, <code>getParent()</code>, <code>getComponents()</code>) directly.</p>
</li>
<li>
<p><strong><code>IComponent::NAME_SEPARATOR</code> removed.</strong> Use <code>IComponent::NameSeparator</code> instead.</p>
</li>
<li>
<p><strong>PHP 8.3 required.</strong></p>
</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 21 Jun 2026 23:34:40 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/component-model/releases/tag/v4.0.0</guid>
	</item>
	<item>
		<title>Bootstrap v3.3.0</title>
		<link>https://github.com/nette/bootstrap/releases/tag/v3.3.0</link>
		<description>A maintenance release that modernizes the foundations: Nette Bootstrap now targets PHP 8.3+ and the latest Nette stack. By dropping legacy compatibility shims, the codebase is leaner and fully covered by mandatory static analysis. Upgrading is mostly a matter of bringing your dependencies up to date.</description>
		<content:encoded><![CDATA[
		<p>A maintenance release that modernizes the foundations: Nette Bootstrap now targets PHP 8.3+ and the latest Nette stack. By dropping legacy compatibility shims, the codebase is leaner and fully covered by mandatory static analysis. Upgrading is mostly a matter of bringing your dependencies up to date.</p>
		]]></content:encoded>
		<pubDate>Sun, 21 Jun 2026 22:22:07 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/bootstrap/releases/tag/v3.3.0</guid>
	</item>
	<item>
		<title>Bootstrap v3.2.9</title>
		<link>https://github.com/nette/bootstrap/releases/tag/v3.2.9</link>
		<description>
Configurator: pass debugMode to MailExtension
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Configurator: pass debugMode to MailExtension</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 21 Jun 2026 22:03:46 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/bootstrap/releases/tag/v3.2.9</guid>
	</item>
	<item>
		<title>Security v3.2.5</title>
		<link>https://github.com/nette/security/releases/tag/v3.2.5</link>
		<description>
fixed compatibility with nette/http 3.4
Identity: use ctype_digit for stricter numeric ID detection
</description>
		<content:encoded><![CDATA[
		<ul>
<li>fixed compatibility with nette/http 3.4</li>
<li>Identity: use ctype_digit for stricter numeric ID detection</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 15 Jun 2026 05:44:10 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/security/releases/tag/v3.2.5</guid>
	</item>
	<item>
		<title>Http v3.4.0</title>
		<link>https://github.com/nette/http/releases/tag/v3.4.0</link>
		<description>The headline is protection against SSRF: the new UrlValidator and IPAddress check a URL before your application fetches it from the server.
💥 Breaking Changes

PHP 8.3 or newer is required
The long-deprecated UserStorage is removed – use Nette\Bridges\SecurityHttp\SessionStorage from nette/security
Request::getRemoteHost() is deprecated and always returns null, as the reverse DNS lookup was slow and unreliable; resolve the host from getRemoteAddress() yourself if you need it (#218)
A number passed as an expiration to setCookie(), setExpiration() and the session is always a relative number of seconds; an absolute Unix timestamp still works but triggers a deprecation, so pass a DateTimeInterface instead

✨ New Features

UrlValidator guards server-side requests against SSRF: it checks the scheme, port, host allow/blocklist and userinfo, and with DNS verifies that the host does not resolve to a private, loopback or other internal address. getResolvedIPs() hands back the verified addresses, so you can pin the connection to them (e.g. via CURLOPT_RESOLVE) and defeat DNS rebinding
IPAddress is an immutable IPv4/IPv6 value object with isPublic(), isPrivate(), isLoopback() and other predicates, CIDR matching via isInRange() and normalization of IPv4-mapped IPv6 addresses
Request::isFrom() checks where a request came from by the Sec-Fetch-Site, Sec-Fetch-Dest and Sec-Fetch-User headers; in browsers without them (Safari &lt; 16.4) it falls back to the strict cookie, so it works everywhere
The SameSite enum replaces the magic strings in setCookie() and Session
Response::setCookie() supports the Partitioned attribute (CHIPS) for third-party cookies, sends Max-Age, which does not depend on the client&apos;s clock, and adds Secure automatically for SameSite=None, which browsers would reject otherwise; deleteCookie() removes the cookie immediately thanks to Max-Age=0

⚠️ Deprecations

IResponse::SameSite* constants – use the SameSite enum
Request::isSameSite() – use isFrom([FetchSite::SameSite, FetchSite::SameOrigin])
Helpers::ipMatch() – use IPAddress::tryFrom($ip)?-&gt;isInRange($mask)
</description>
		<content:encoded><![CDATA[
		<p>The headline is protection against SSRF: the new <code>UrlValidator</code> and <code>IPAddress</code> check a URL before your application fetches it from the server.</p>
<h2>💥 Breaking Changes</h2>
<ul>
<li>PHP 8.3 or newer is required</li>
<li>The long-deprecated <strong>UserStorage</strong> is removed – use <code>Nette\Bridges\SecurityHttp\SessionStorage</code> from nette/security</li>
<li><strong>Request::getRemoteHost()</strong> is deprecated and always returns <code>null</code>, as the reverse DNS lookup was slow and unreliable; resolve the host from <code>getRemoteAddress()</code> yourself if you need it (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1438535664" data-permission-text="Title is private" data-url="https://github.com/nette/http/issues/218" data-hovercard-type="issue" data-hovercard-url="/nette/http/issues/218/hovercard" href="https://github.com/nette/http/issues/218">#218</a>)</li>
<li>A number passed as an expiration to <code>setCookie()</code>, <code>setExpiration()</code> and the session is always a relative number of seconds; an absolute Unix timestamp still works but triggers a deprecation, so pass a <code>DateTimeInterface</code> instead</li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>UrlValidator</strong> guards server-side requests against SSRF: it checks the scheme, port, host allow/blocklist and userinfo, and with DNS verifies that the host does not resolve to a private, loopback or other internal address. <strong>getResolvedIPs()</strong> hands back the verified addresses, so you can pin the connection to them (e.g. via <code>CURLOPT_RESOLVE</code>) and defeat DNS rebinding</li>
<li><strong>IPAddress</strong> is an immutable IPv4/IPv6 value object with <code>isPublic()</code>, <code>isPrivate()</code>, <code>isLoopback()</code> and other predicates, CIDR matching via <code>isInRange()</code> and normalization of IPv4-mapped IPv6 addresses</li>
<li><strong>Request::isFrom()</strong> checks where a request came from by the <code>Sec-Fetch-Site</code>, <code>Sec-Fetch-Dest</code> and <code>Sec-Fetch-User</code> headers; in browsers without them (Safari &lt; 16.4) it falls back to the strict cookie, so it works everywhere</li>
<li>The <strong>SameSite</strong> enum replaces the magic strings in <code>setCookie()</code> and <code>Session</code></li>
<li><strong>Response::setCookie()</strong> supports the <code>Partitioned</code> attribute (CHIPS) for third-party cookies, sends <code>Max-Age</code>, which does not depend on the client's clock, and adds <code>Secure</code> automatically for <code>SameSite=None</code>, which browsers would reject otherwise; <strong>deleteCookie()</strong> removes the cookie immediately thanks to <code>Max-Age=0</code></li>
</ul>
<h2><g-emoji class="g-emoji" alias="warning">⚠️</g-emoji> Deprecations</h2>
<ul>
<li><code>IResponse::SameSite*</code> constants – use the <code>SameSite</code> enum</li>
<li><code>Request::isSameSite()</code> – use <code>isFrom([FetchSite::SameSite, FetchSite::SameOrigin])</code></li>
<li><code>Helpers::ipMatch()</code> – use <code>IPAddress::tryFrom($ip)?-&gt;isInRange($mask)</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Sat, 13 Jun 2026 01:09:27 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/http/releases/tag/v3.4.0</guid>
	</item>
	<item>
		<title>Application v3.2.10</title>
		<link>https://github.com/nette/application/releases/tag/v3.2.10</link>
		<description>
Sharper phpDoc types and descriptions throughout the codebase
Reverted the experimental hasPresenter()/getPresenterIfExists() addition and the $throw deprecation in Component/Form::getPresenter() – the previous API behavior stays unchanged
{layout auto} no longer triggers infinite recursion – when used inside a referring template, the layout finder is now skipped instead of looping back on itself
Response and router classes now use promoted readonly properties, trimming boilerplate across Application, FileResponse, JsonResponse, RedirectResponse, TextResponse, ForwardResponse and CliRouter
Callback parameters in PresenterFactory, CallbackResponse and Multiplier are normalized to Closure for stronger typing
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Sharper phpDoc types and descriptions throughout the codebase</li>
<li>Reverted the experimental <code>hasPresenter()/getPresenterIfExists()</code> addition and the <code>$throw</code> deprecation in <code>Component</code>/<code>Form::getPresenter()</code> – the previous API behavior stays unchanged</li>
<li><strong>{layout auto}</strong> no longer triggers infinite recursion – when used inside a referring template, the layout finder is now skipped instead of looping back on itself</li>
<li>Response and router classes now use <strong>promoted readonly properties</strong>, trimming boilerplate across <code>Application</code>, <code>FileResponse</code>, <code>JsonResponse</code>, <code>RedirectResponse</code>, <code>TextResponse</code>, <code>ForwardResponse</code> and <code>CliRouter</code></li>
<li>Callback parameters in <code>PresenterFactory</code>, <code>CallbackResponse</code> and <code>Multiplier</code> are normalized to <strong><code>Closure</code></strong> for stronger typing</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 01 Jun 2026 18:34:36 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.2.10</guid>
	</item>
	<item>
		<title>Http v3.3.4</title>
		<link>https://github.com/nette/http/releases/tag/v3.3.4</link>
		<description>
RequestFactory::setForceHttps() – force the request scheme to HTTPS regardless of the server environment, handy behind proxies and load balancers that don&apos;t advertise TLS termination. Also exposed via the DI config option http: forceHttps: true.
Request::getOrigin() now strictly follows RFC 6454 – returns null for any Origin header that isn&apos;t a bare scheme://host[:port] (e.g. headers containing a path are rejected instead of being silently accepted).
Improved phpDoc types and descriptions across the whole Nette\Http namespace – better IDE autocompletion and PHPStan inference for Request, Response, Session, Url and friends.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>RequestFactory::setForceHttps()</strong> – force the request scheme to HTTPS regardless of the server environment, handy behind proxies and load balancers that don't advertise TLS termination. Also exposed via the DI config option <code>http: forceHttps: true</code>.</li>
<li><strong>Request::getOrigin()</strong> now strictly follows RFC 6454 – returns <code>null</code> for any <code>Origin</code> header that isn't a bare <code>scheme://host[:port]</code> (e.g. headers containing a path are rejected instead of being silently accepted).</li>
<li>Improved phpDoc types and descriptions across the whole <code>Nette\Http</code> namespace – better IDE autocompletion and PHPStan inference for <code>Request</code>, <code>Response</code>, <code>Session</code>, <code>Url</code> and friends.</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 26 May 2026 16:58:49 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/http/releases/tag/v3.3.4</guid>
	</item>
	<item>
		<title>Forms v3.2.9</title>
		<link>https://github.com/nette/forms/releases/tag/v3.2.9</link>
		<description>A maintenance-focused release that tightens type safety across the whole codebase, modernizes the JavaScript test stack, and turns static analysis into a non-negotiable part of the build. No API changes – just a more solid foundation under the hood.

Native types everywhere – filled in missing native type declarations across Container, BaseControl, Validator, Rules, Form and friends, so PHPStan (and your IDE) see the real shape of things
Sharper phpDoc – tightened phpDoc types and descriptions throughout, giving better autocomplete and clearer intent at every call - Reorganized a few tests and switched some over to allowCrossOrigin() for clarity
</description>
		<content:encoded><![CDATA[
		<p>A maintenance-focused release that tightens type safety across the whole codebase, modernizes the JavaScript test stack, and turns static analysis into a non-negotiable part of the build. No API changes – just a more solid foundation under the hood.</p>
<ul>
<li><strong>Native types everywhere</strong> – filled in missing native type declarations across <code>Container</code>, <code>BaseControl</code>, <code>Validator</code>, <code>Rules</code>, <code>Form</code> and friends, so PHPStan (and your IDE) see the real shape of things</li>
<li><strong>Sharper phpDoc</strong> – tightened phpDoc types and descriptions throughout, giving better autocomplete and clearer intent at every call - Reorganized a few tests and switched some over to <code>allowCrossOrigin()</code> for clarity</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 26 May 2026 12:17:13 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/forms/releases/tag/v3.2.9</guid>
	</item>
	<item>
		<title>Component Model v3.2.0</title>
		<link>https://github.com/nette/component-model/releases/tag/v3.2.0</link>
		<description>A transitional release ahead of 4.0. Nothing is removed yet, this version just lights up deprecation notices on things that will disappear in 4.0, so you can get your code ready in peace.
💥 Deprecated (will be removed in 4.0)

Magic properties Component::$name, Component::$parent and Container::$components – use getName(), getParent(), getComponents() instead.
Calling monitor($type) without callbacks – pass them directly: monitor($type, $attached, $detached). Overriding attached() / detached() in subclasses is on its way out.
Constant IComponent::NAME_SEPARATOR – switch to IComponent::NameSeparator (the deprecation is now reported via the native #[\Deprecated] attribute).
</description>
		<content:encoded><![CDATA[
		<p>A transitional release ahead of 4.0. Nothing is removed yet, this version just lights up deprecation notices on things that will disappear in 4.0, so you can get your code ready in peace.</p>
<h2>💥 Deprecated (will be removed in 4.0)</h2>
<ul>
<li>Magic properties <code>Component::$name</code>, <code>Component::$parent</code> and <code>Container::$components</code> – use <code>getName()</code>, <code>getParent()</code>, <code>getComponents()</code> instead.</li>
<li>Calling <code>monitor($type)</code> without callbacks – pass them directly: <code>monitor($type, $attached, $detached)</code>. Overriding <code>attached()</code> / <code>detached()</code> in subclasses is on its way out.</li>
<li>Constant <code>IComponent::NAME_SEPARATOR</code> – switch to <code>IComponent::NameSeparator</code> (the deprecation is now reported via the native <code>#[\Deprecated]</code> attribute).</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 26 May 2026 10:39:52 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/component-model/releases/tag/v3.2.0</guid>
	</item>
	<item>
		<title>Mail v4.1.2</title>
		<link>https://github.com/nette/mail/releases/tag/v4.1.2</link>
		<description>
Interceptor – a new mailer wrapper that redirects all outgoing To/Cc/Bcc (plus read-receipt headers) to one fixed address, preserves the originals in X-Original-* headers, and optionally adds a subject prefix. No more sending test mail to real customers by accident. Wire it via DI with mail.redirect: dev@example.com and it slots in automatically.
MailTracy Bar panel – a new Bridges/MailTracy/MailPanel subscribes to Interceptor::$onSent and lists each sent message (From / To+Cc+Bcc / Subject / Status) right in the Tracy Bar. Auto-registers in debug mode whenever the Interceptor is active; opt in or out explicitly with mail: debugger: true|false.
HtmlComposer – a standalone HTML pre-processing pipeline you can drive directly: opt in to inlineCss() (accumulates stylesheets across calls), embedImages($basePath), and let it handle &lt;title&gt; to subject extraction and plain-text alternative generation. Message::setHtmlBody() keeps working as a BC-friendly facade.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Interceptor</strong> – a new mailer wrapper that redirects all outgoing <code>To</code>/<code>Cc</code>/<code>Bcc</code> (plus read-receipt headers) to one fixed address, preserves the originals in <code>X-Original-*</code> headers, and optionally adds a subject prefix. No more sending test mail to real customers by accident. Wire it via DI with <code>mail.redirect: dev@example.com</code> and it slots in automatically.</li>
<li><strong>MailTracy Bar panel</strong> – a new <code>Bridges/MailTracy/MailPanel</code> subscribes to <code>Interceptor::$onSent</code> and lists each sent message (From / To+Cc+Bcc / Subject / Status) right in the Tracy Bar. Auto-registers in debug mode whenever the Interceptor is active; opt in or out explicitly with <code>mail: debugger: true|false</code>.</li>
<li><strong><code>HtmlComposer</code></strong> – a standalone HTML pre-processing pipeline you can drive directly: opt in to <code>inlineCss()</code> (accumulates stylesheets across calls), <code>embedImages($basePath)</code>, and let it handle <code>&lt;title&gt;</code> to subject extraction and plain-text alternative generation. <code>Message::setHtmlBody()</code> keeps working as a BC-friendly facade.</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 19 May 2026 17:58:24 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.1.2</guid>
	</item>
	<item>
		<title>Caching v3.4.2</title>
		<link>https://github.com/nette/caching/releases/tag/v3.4.2</link>
		<description>A housekeeping release focused on code quality: every class and method now carries clearer, more descriptive PHPDoc, type hints got sharper (both native and annotated), and static analysis is now a mandatory part of CI with the official Nette PHPStan rules. No API changes – just a tidier, better-typed codebase.</description>
		<content:encoded><![CDATA[
		<p>A housekeeping release focused on code quality: every class and method now carries clearer, more descriptive PHPDoc, type hints got sharper (both native and annotated), and static analysis is now a mandatory part of CI with the official Nette PHPStan rules. No API changes – just a tidier, better-typed codebase.</p>
		]]></content:encoded>
		<pubDate>Tue, 12 May 2026 01:33:41 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/caching/releases/tag/v3.4.2</guid>
	</item>
	<item>
		<title>Neon v3.4.8</title>
		<link>https://github.com/nette/neon/releases/tag/v3.4.8</link>
		<description>
More precise phpDoc types across the codebase – better autocompletion and stricter static analysis
Improved phpDoc descriptions for the public API
</description>
		<content:encoded><![CDATA[
		<ul>
<li>More precise phpDoc types across the codebase – better autocompletion and stricter static analysis</li>
<li>Improved phpDoc descriptions for the public API</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 11 May 2026 21:43:26 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v3.4.8</guid>
	</item>
	<item>
		<title>Security v3.2.4</title>
		<link>https://github.com/nette/security/releases/tag/v3.2.4</link>
		<description>

Guest identity – an IdentityHandler authenticator may now implement getGuestIdentity(): ?IIdentity to hand anonymous visitors a real identity. When present, getIdentity(), getId() and getRoles() transparently fall back to it, so guests carry their own roles and data instead of just the $guestRole string. The guest identity is resolved on read only and never written to storage.


$persistIdentity – the new User::$persistIdentity property lets you decide what happens to the identity after logout or expiration. It stays available for personalization by default; flip it to false and getIdentity()/getId() return null once the user is no longer logged in. Configurable straight from the security.authentication DI section.


SessionStorage no longer refreshes the sliding expiration timestamp once the session has already expired – an expired identity stays expired instead of being silently kept alive for another round


Adopted nette/phpstan-rules and made static analysis a mandatory part of the build, then resolved the errors it surfaced


Improved phpDoc types and descriptions across the codebase

</description>
		<content:encoded><![CDATA[
		<ul>
<li>
<p><strong>Guest identity</strong> – an <code>IdentityHandler</code> authenticator may now implement <code>getGuestIdentity(): ?IIdentity</code> to hand anonymous visitors a real identity. When present, <code>getIdentity()</code>, <code>getId()</code> and <code>getRoles()</code> transparently fall back to it, so guests carry their own roles and data instead of just the <code>$guestRole</code> string. The guest identity is resolved on read only and never written to storage.</p>
</li>
<li>
<p><strong>$persistIdentity</strong> – the new <code>User::$persistIdentity</code> property lets you decide what happens to the identity after logout or expiration. It stays available for personalization by default; flip it to <code>false</code> and <code>getIdentity()</code>/<code>getId()</code> return <code>null</code> once the user is no longer logged in. Configurable straight from the <code>security.authentication</code> DI section.</p>
</li>
<li>
<p><strong>SessionStorage</strong> no longer refreshes the sliding expiration timestamp once the session has already expired – an expired identity stays expired instead of being silently kept alive for another round</p>
</li>
<li>
<p>Adopted <code>nette/phpstan-rules</code> and made static analysis a mandatory part of the build, then resolved the errors it surfaced</p>
</li>
<li>
<p>Improved phpDoc types and descriptions across the codebase</p>
</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 11 May 2026 21:19:01 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/security/releases/tag/v3.2.4</guid>
	</item>
	<item>
		<title>Utils v4.1.4</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.4</link>
		<description>
Process – a new class for starting and controlling external processes: read their output, feed them input, pipe one process into another, wait for completion, terminate, and check exit codes. Process::runExecutable() passes arguments as an array so there&apos;s zero shell involvement and no risk of shell injection, while Process::runCommand() is there when you really do want the shell. Comes with timeouts, incremental output consumption (consumeStdOutput() / consumeStdError()), and works on Windows too.
FileSystem::isValidFilename() – quickly check whether a string is a safe, cross-platform filename: it rejects path separators, control and reserved characters, trailing dots or spaces, and Windows device names like CON or LPT1.
Image::fromFile() and Image::fromString() now accept an optional $warnings parameter – pass it in and any GD warnings are handed back to you as a string instead of being emitted as a PHP warning, so you can log or display them on your own terms.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Process</strong> – a new class for starting and controlling external processes: read their output, feed them input, pipe one process into another, wait for completion, terminate, and check exit codes. <code>Process::runExecutable()</code> passes arguments as an array so there's zero shell involvement and no risk of shell injection, while <code>Process::runCommand()</code> is there when you really do want the shell. Comes with timeouts, incremental output consumption (<code>consumeStdOutput()</code> / <code>consumeStdError()</code>), and works on Windows too.</li>
<li><strong>FileSystem::isValidFilename()</strong> – quickly check whether a string is a safe, cross-platform filename: it rejects path separators, control and reserved characters, trailing dots or spaces, and Windows device names like <code>CON</code> or <code>LPT1</code>.</li>
<li><strong>Image::fromFile()</strong> and <strong>Image::fromString()</strong> now accept an optional <code>$warnings</code> parameter – pass it in and any GD warnings are handed back to you as a string instead of being emitted as a PHP warning, so you can log or display them on your own terms.</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 11 May 2026 20:59:10 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.4</guid>
	</item>
	<item>
		<title>Tester v2.6.1</title>
		<link>https://github.com/nette/tester/releases/tag/v2.6.1</link>
		<description>
PhpInterpreter now passes the command to proc_open() as an array, so PHP handles argument escaping itself and the subshell is bypassed on Linux too – fewer surprises with paths and arguments containing spaces or special characters
Test::getResult() throws a LogicException instead of silently returning an unset value when the test hasn&apos;t finished running yet – mistakes surface immediately rather than turning into puzzling downstream errors
Improved PHPDoc types and descriptions throughout the framework for better IDE hints and static analysis
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>PhpInterpreter</strong> now passes the command to <code>proc_open()</code> as an array, so PHP handles argument escaping itself and the subshell is bypassed on Linux too – fewer surprises with paths and arguments containing spaces or special characters</li>
<li><strong>Test::getResult()</strong> throws a <code>LogicException</code> instead of silently returning an unset value when the test hasn't finished running yet – mistakes surface immediately rather than turning into puzzling downstream errors</li>
<li>Improved PHPDoc types and descriptions throughout the framework for better IDE hints and static analysis</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 11 May 2026 18:21:48 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tester/releases/tag/v2.6.1</guid>
	</item>
	<item>
		<title>Di v3.2.6</title>
		<link>https://github.com/nette/di/releases/tag/v3.2.6</link>
		<description>A maintenance release laser-focused on type safety. Static analysis is now mandatory in CI, the codebase ships richer native and PHPDoc types, and the Tracy DI panel got a cleaner Latte rewrite. No behavioral changes – just a sturdier foundation for everything built on top.

Native types – tightened parameter and return types across Compiler, ContainerLoader, ServiceDefinition and friends
ContainerPanel – Tracy panel template rewritten with n:attributes for noticeably cleaner Latte syntax
PHPStan-clean codebase – wide-ranging cleanup across DI internals so the whole tree passes strict analysis
Richer PHPDoc – improved @param, @return and class descriptions across Compiler, Container, ContainerBuilder, Resolver, Helpers, definitions and extensions, giving IDEs and static analyzers far more to work with
Better generic types – sharpened PHPDoc generics in autowiring, container builder, definitions and resolver
</description>
		<content:encoded><![CDATA[
		<p>A maintenance release laser-focused on type safety. Static analysis is now mandatory in CI, the codebase ships richer native and PHPDoc types, and the Tracy DI panel got a cleaner Latte rewrite. No behavioral changes – just a sturdier foundation for everything built on top.</p>
<ul>
<li><strong>Native types</strong> – tightened parameter and return types across <code>Compiler</code>, <code>ContainerLoader</code>, <code>ServiceDefinition</code> and friends</li>
<li><strong>ContainerPanel</strong> – Tracy panel template rewritten with <code>n:attributes</code> for noticeably cleaner Latte syntax</li>
<li><strong>PHPStan-clean codebase</strong> – wide-ranging cleanup across DI internals so the whole tree passes strict analysis</li>
<li><strong>Richer PHPDoc</strong> – improved <code>@param</code>, <code>@return</code> and class descriptions across <code>Compiler</code>, <code>Container</code>, <code>ContainerBuilder</code>, <code>Resolver</code>, <code>Helpers</code>, definitions and extensions, giving IDEs and static analyzers far more to work with</li>
<li><strong>Better generic types</strong> – sharpened PHPDoc generics in autowiring, container builder, definitions and resolver</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 06 May 2026 01:46:54 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/di/releases/tag/v3.2.6</guid>
	</item>
	<item>
		<title>Component Model v3.1.4</title>
		<link>https://github.com/nette/component-model/releases/tag/v3.1.4</link>
		<description>A focused maintenance release for the Component layer. The headline is hardening of the monitor callback machinery: nested re-entry is now safely guarded, callbacks are normalized to \Closure for consistent deduplication, and the whole codebase has been brought under mandatory static analysis with nette/phpstan-rules.

Reentry protection for monitor callbacks – Component::refreshMonitors() now refuses to re-enter itself while listeners are running. If a listener removes and re-adds the same component (or otherwise triggers another refresh), each component is processed exactly once instead of looping or double-firing.
Reliable callback deduplication – switched the in-array check for monitor callbacks to loose comparison. Closures are never === to each other unless they are literally the same instance, so the previous strict check silently let duplicates through.
Adopted nette/phpstan-rules – stricter ruleset enabled, with a dedicated tests/types/component-types.php driving type tests.
</description>
		<content:encoded><![CDATA[
		<p>A focused maintenance release for the Component layer. The headline is hardening of the monitor callback machinery: nested re-entry is now safely guarded, callbacks are normalized to <code>\Closure</code> for consistent deduplication, and the whole codebase has been brought under mandatory static analysis with <code>nette/phpstan-rules</code>.</p>
<ul>
<li><strong>Reentry protection for monitor callbacks</strong> – <code>Component::refreshMonitors()</code> now refuses to re-enter itself while listeners are running. If a listener removes and re-adds the same component (or otherwise triggers another refresh), each component is processed exactly once instead of looping or double-firing.</li>
<li><strong>Reliable callback deduplication</strong> – switched the in-array check for monitor callbacks to loose comparison. Closures are never <code>===</code> to each other unless they are literally the same instance, so the previous strict check silently let duplicates through.</li>
<li><strong>Adopted <code>nette/phpstan-rules</code></strong> – stricter ruleset enabled, with a dedicated <code>tests/types/component-types.php</code> driving type tests.</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 06 May 2026 01:07:58 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/component-model/releases/tag/v3.1.4</guid>
	</item>
	<item>
		<title>Bootstrap v3.2.8</title>
		<link>https://github.com/nette/bootstrap/releases/tag/v3.2.8</link>
		<description>
Default parameters are now overridable in user configs – previously wwwDir: %rootDir%/www in common.neon was silently overwritten because defaults were injected after user configs.
%baseUrl% no longer crashes when HttpExtension is missing – the parameter is now a lazy statement resolved at runtime instead of a hard reference at compile time (#75).
Improved PHPDoc descriptions and types across the codebase.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Default parameters are now overridable in user configs</strong> – previously <code>wwwDir: %rootDir%/www</code> in <code>common.neon</code> was silently overwritten because defaults were injected <em>after</em> user configs.</li>
<li><strong><code>%baseUrl%</code> no longer crashes when <code>HttpExtension</code> is missing</strong> – the parameter is now a lazy statement resolved at runtime instead of a hard reference at compile time (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3382528776" data-permission-text="Title is private" data-url="https://github.com/nette/bootstrap/issues/75" data-hovercard-type="issue" data-hovercard-url="/nette/bootstrap/issues/75/hovercard" href="https://github.com/nette/bootstrap/issues/75">#75</a>).</li>
<li>Improved PHPDoc descriptions and types across the codebase.</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 05 May 2026 21:32:56 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/bootstrap/releases/tag/v3.2.8</guid>
	</item>
	<item>
		<title>Tracy v2.12.0</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.12.0</link>
		<description>Tracy now talks to AI agents. When a coding assistant drives a browser through your app, it gets the error page, the Bar and your dumps as compact markdown instead of HTML, so it sees exactly what went wrong without digging through markup.

AI agents – Tracy recognizes a browser driven by an agent (navigator.webdriver) and serves it markdown: the BlueScreen, the Bar including the Warnings and Dumps panels, and dump(), whose output goes to the browser console where the agent reads it
Markdown error logs – every logged exception gets a .md file next to its HTML report, readable by agents and humans alike
Production error page – tells the agent in the console whether the error was logged on the server, so it does not have to guess behind a bare 500
Logged from – exception reports show the line where Debugger::log() was called
Debugger::$transparentPaths – one list of framework paths (Tracy, Nette and Latte are detected automatically) whose frames Tracy skips when locating the real call site and collapses in the BlueScreen stack trace; BlueScreen::$collapsePaths is deprecated but still works
The Dumper supports php-ds 2.0
</description>
		<content:encoded><![CDATA[
		<p>Tracy now talks to AI agents. When a coding assistant drives a browser through your app, it gets the error page, the Bar and your dumps as compact markdown instead of HTML, so it sees exactly what went wrong without digging through markup.</p>
<ul>
<li><strong>AI agents</strong> – Tracy recognizes a browser driven by an agent (<code>navigator.webdriver</code>) and serves it markdown: the BlueScreen, the Bar including the Warnings and Dumps panels, and <code>dump()</code>, whose output goes to the browser console where the agent reads it</li>
<li><strong>Markdown error logs</strong> – every logged exception gets a <code>.md</code> file next to its HTML report, readable by agents and humans alike</li>
<li><strong>Production error page</strong> – tells the agent in the console whether the error was logged on the server, so it does not have to guess behind a bare 500</li>
<li><strong>Logged from</strong> – exception reports show the line where <code>Debugger::log()</code> was called</li>
<li><strong>Debugger::$transparentPaths</strong> – one list of framework paths (Tracy, Nette and Latte are detected automatically) whose frames Tracy skips when locating the real call site and collapses in the BlueScreen stack trace; <code>BlueScreen::$collapsePaths</code> is deprecated but still works</li>
<li>The Dumper supports php-ds 2.0</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 04 May 2026 00:28:31 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.12.0</guid>
	</item>
	<item>
		<title>Mail v4.1.1</title>
		<link>https://github.com/nette/mail/releases/tag/v4.1.1</link>
		<description>🐛 Bug Fixes

Message::setHtmlBody() – survives large inline data: URIs. A &gt;500 kB base64 payload used to exhaust PCRE&apos;s backtrack limit and abort the whole send; the regex is now backtracking-free (#79)
Message::setHtmlBody() – embeds images whose quoted src=&quot;…&quot; or url(&apos;…&apos;) contains spaces, like &quot;holiday photos/beach.jpg&quot; (#97)
Message::setHtmlBody() – embeds images whose quoted path contains parentheses, so the classic screenshot (1).png naming no longer silently breaks (#89)
SendmailMailer – signs the full message so DKIM now covers Subject and To headers, closing a deliverability gap at Gmail, Outlook, and other strict providers (#99)
MimePart – quotes address phrases containing special characters before MIME-encoding, producing spec-compliant headers even when names include commas, angle brackets, or quotes (#102)
CssInliner – gracefully skips selectors the DOM engine can&apos;t evaluate; pseudo-classes and pseudo-elements like ::marker, :hover, :checked no longer break inlining
CssInliner – tokenizer regex fixed for very long strings and invalid url() quote combinations that previously tripped the parser
</description>
		<content:encoded><![CDATA[
		<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong>Message::setHtmlBody()</strong> – survives large inline <code>data:</code> URIs. A &gt;500 kB base64 payload used to exhaust PCRE's backtrack limit and abort the whole send; the regex is now backtracking-free (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="775323261" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/79" data-hovercard-type="issue" data-hovercard-url="/nette/mail/issues/79/hovercard" href="https://github.com/nette/mail/issues/79">#79</a>)</li>
<li><strong>Message::setHtmlBody()</strong> – embeds images whose quoted <code>src="…"</code> or <code>url('…')</code> contains spaces, like <code>"holiday photos/beach.jpg"</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2088766719" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/97" data-hovercard-type="issue" data-hovercard-url="/nette/mail/issues/97/hovercard" href="https://github.com/nette/mail/issues/97">#97</a>)</li>
<li><strong>Message::setHtmlBody()</strong> – embeds images whose quoted path contains parentheses, so the classic <code>screenshot (1).png</code> naming no longer silently breaks (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1320705520" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/89" data-hovercard-type="issue" data-hovercard-url="/nette/mail/issues/89/hovercard" href="https://github.com/nette/mail/issues/89">#89</a>)</li>
<li><strong>SendmailMailer</strong> – signs the full message so DKIM now covers <code>Subject</code> and <code>To</code> headers, closing a deliverability gap at Gmail, Outlook, and other strict providers (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2255162594" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/99" data-hovercard-type="issue" data-hovercard-url="/nette/mail/issues/99/hovercard" href="https://github.com/nette/mail/issues/99">#99</a>)</li>
<li><strong>MimePart</strong> – quotes address phrases containing special characters before MIME-encoding, producing spec-compliant headers even when names include commas, angle brackets, or quotes (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2578128385" data-permission-text="Title is private" data-url="https://github.com/nette/mail/issues/102" data-hovercard-type="pull_request" data-hovercard-url="/nette/mail/pull/102/hovercard" href="https://github.com/nette/mail/pull/102">#102</a>)</li>
<li><strong>CssInliner</strong> – gracefully skips selectors the DOM engine can't evaluate; pseudo-classes and pseudo-elements like <code>::marker</code>, <code>:hover</code>, <code>:checked</code> no longer break inlining</li>
<li><strong>CssInliner</strong> – tokenizer regex fixed for very long strings and invalid <code>url()</code> quote combinations that previously tripped the parser</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 23 Apr 2026 22:32:00 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.1.1</guid>
	</item>
	<item>
		<title>Latte v3.1.4</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.4</link>
		<description>💥 Breaking Changes

|limit lost its second argument, the offset, which was added in 3.1.3; to skip items use |slice
For extensions working with the AST: $elseLine of ForeachNode, FirstLastSepNode and IfChangedNode is gone and SwitchNode::$cases no longer holds positions; read the positions of the tags from the new StatementNode::$tagRanges

✨ New Features

|limit works on strings too
Tokens and nodes carry their whole source span, not just the start, and StatementNode::$tagRanges gives the exact location of each tag of a paired statement – a base for editor integrations and precise error reporting

🐛 Bug Fixes

Feature::Dedent handles inline content correctly (#412, #413, #414)
Template linting with PhpHelpers::checkCode() works when the PHP binary lives in a path with spaces (#415)
A template with a multi-line name compiles to valid PHP
</description>
		<content:encoded><![CDATA[
		<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>|limit</strong> lost its second argument, the offset, which was added in 3.1.3; to skip items use <code>|slice</code></li>
<li>For extensions working with the AST: <code>$elseLine</code> of <code>ForeachNode</code>, <code>FirstLastSepNode</code> and <code>IfChangedNode</code> is gone and <code>SwitchNode::$cases</code> no longer holds positions; read the positions of the tags from the new <code>StatementNode::$tagRanges</code></li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>|limit</strong> works on strings too</li>
<li>Tokens and nodes carry their whole source span, not just the start, and <strong>StatementNode::$tagRanges</strong> gives the exact location of each tag of a paired statement – a base for editor integrations and precise error reporting</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><code>Feature::Dedent</code> handles inline content correctly (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4133019498" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/412" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/412/hovercard" href="https://github.com/nette/latte/issues/412">#412</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4133242494" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/413" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/413/hovercard" href="https://github.com/nette/latte/issues/413">#413</a>, <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4204623353" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/414" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/414/hovercard" href="https://github.com/nette/latte/pull/414">#414</a>)</li>
<li>Template linting with <code>PhpHelpers::checkCode()</code> works when the PHP binary lives in a path with spaces (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4232958618" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/415" data-hovercard-type="pull_request" data-hovercard-url="/nette/latte/pull/415/hovercard" href="https://github.com/nette/latte/pull/415">#415</a>)</li>
<li>A template with a multi-line name compiles to valid PHP</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 23 Apr 2026 06:05:58 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.4</guid>
	</item>
	<item>
		<title>Tracy v2.11.4</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.11.4</link>
		<description>A maintenance release focused on CSP-friendly assets, mobile-friendly error pages, and a couple of handy API additions. Expect cleaner nonce handling, better behavior on phones, and a bar.js that no longer trips strict Content Security Policies.

script-src-elem support in Helpers::getNonce() – nonces are now also picked up from the script-src-elem CSP directive, not just script-src (#612).
CSP-friendly Tracy Bar – replaced the inline onload attribute in bar.js with a native addEventListener, eliminating a common CSP violation (#614).
FileSession::clean() – emits a warning when the session directory is not readable, making misconfigured storage easier to diagnose (#538).
Mobile-friendly error pages – BlueScreen and the 500 error template now include a proper viewport meta tag, so exceptions no longer render microscopically on phones (#604).
Improved PHPDoc descriptions and fixed PHPStan errors across the codebase.
open-in-editor on Windows – installer now registers the protocol via AutoLaunchProtocolsFromOrigins, suppressing the browser&apos;s &quot;Open external app?&quot; confirmation prompt (#573).
</description>
		<content:encoded><![CDATA[
		<p>A maintenance release focused on CSP-friendly assets, mobile-friendly error pages, and a couple of handy API additions. Expect cleaner nonce handling, better behavior on phones, and a bar.js that no longer trips strict Content Security Policies.</p>
<ul>
<li><strong>script-src-elem support in Helpers::getNonce()</strong> – nonces are now also picked up from the <code>script-src-elem</code> CSP directive, not just <code>script-src</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3958438647" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/612" data-hovercard-type="pull_request" data-hovercard-url="/nette/tracy/pull/612/hovercard" href="https://github.com/nette/tracy/pull/612">#612</a>).</li>
<li><strong>CSP-friendly Tracy Bar</strong> – replaced the inline <code>onload</code> attribute in bar.js with a native <code>addEventListener</code>, eliminating a common CSP violation (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4164090884" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/614" data-hovercard-type="issue" data-hovercard-url="/nette/tracy/issues/614/hovercard" href="https://github.com/nette/tracy/issues/614">#614</a>).</li>
<li><strong>FileSession::clean()</strong> – emits a warning when the session directory is not readable, making misconfigured storage easier to diagnose (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1179574698" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/538" data-hovercard-type="issue" data-hovercard-url="/nette/tracy/issues/538/hovercard" href="https://github.com/nette/tracy/issues/538">#538</a>).</li>
<li><strong>Mobile-friendly error pages</strong> – BlueScreen and the 500 error template now include a proper viewport meta tag, so exceptions no longer render microscopically on phones (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3500373316" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/604" data-hovercard-type="pull_request" data-hovercard-url="/nette/tracy/pull/604/hovercard" href="https://github.com/nette/tracy/pull/604">#604</a>).</li>
<li>Improved PHPDoc descriptions and fixed PHPStan errors across the codebase.</li>
<li><strong>open-in-editor on Windows</strong> – installer now registers the protocol via <code>AutoLaunchProtocolsFromOrigins</code>, suppressing the browser's "Open external app?" confirmation prompt (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1936474315" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/573" data-hovercard-type="pull_request" data-hovercard-url="/nette/tracy/pull/573/hovercard" href="https://github.com/nette/tracy/pull/573">#573</a>).</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 22 Apr 2026 06:05:29 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.11.4</guid>
	</item>
	<item>
		<title>Database v3.2.9</title>
		<link>https://github.com/nette/database/releases/tag/v3.2.9</link>
		<description>This release brings a set of focused exception types that let you catch specific database failure modes (deadlocks, lock timeouts, check constraint violations, lost connections) instead of wrestling with generic driver errors. ActiveRow and Selection now expose getExplorer() for direct access to the underlying Explorer, and the reflection layer has been refactored for more consistent metadata across drivers.
✨ New Features

getExplorer() – ActiveRow and Selection now expose the underlying Explorer instance, no more jumping through hoops to get back to it
DeadlockException – catch deadlocks and serialization failures distinctly from other driver errors, so retry logic can stay surgical
LockTimeoutException – a dedicated exception for lock wait timeouts
CheckConstraintViolationException – check constraint violations now get their own class instead of being lumped with generic constraint errors
ConnectionLostException – distinguish dropped connections from other driver failures, making reconnect strategies much cleaner
Docker Compose setup – a ready-to-run Compose configuration for spinning up test databases locally

♻️ Code Refactoring

Drivers reflection output – unified FK row shape across drivers, simplified MsSql getIndexes SQL, parameterized SQLite PRAGMA queries, and ForeignKey::$name is now a non-nullable string

📦 Maintenance

Improved PHPDoc descriptions, phpDoc types, and native type declarations across the codebase
</description>
		<content:encoded><![CDATA[
		<p>This release brings a set of focused exception types that let you catch specific database failure modes (deadlocks, lock timeouts, check constraint violations, lost connections) instead of wrestling with generic driver errors. ActiveRow and Selection now expose <code>getExplorer()</code> for direct access to the underlying Explorer, and the reflection layer has been refactored for more consistent metadata across drivers.</p>
<h2>✨ New Features</h2>
<ul>
<li><strong>getExplorer()</strong> – <code>ActiveRow</code> and <code>Selection</code> now expose the underlying <code>Explorer</code> instance, no more jumping through hoops to get back to it</li>
<li><strong>DeadlockException</strong> – catch deadlocks and serialization failures distinctly from other driver errors, so retry logic can stay surgical</li>
<li><strong>LockTimeoutException</strong> – a dedicated exception for lock wait timeouts</li>
<li><strong>CheckConstraintViolationException</strong> – check constraint violations now get their own class instead of being lumped with generic constraint errors</li>
<li><strong>ConnectionLostException</strong> – distinguish dropped connections from other driver failures, making reconnect strategies much cleaner</li>
<li><strong>Docker Compose setup</strong> – a ready-to-run Compose configuration for spinning up test databases locally</li>
</ul>
<h2>♻️ Code Refactoring</h2>
<ul>
<li><strong>Drivers reflection output</strong> – unified FK row shape across drivers, simplified MsSql <code>getIndexes</code> SQL, parameterized SQLite PRAGMA queries, and <code>ForeignKey::$name</code> is now a non-nullable string</li>
</ul>
<h2>📦 Maintenance</h2>
<ul>
<li>Improved PHPDoc descriptions, phpDoc types, and native type declarations across the codebase</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 22 Apr 2026 05:29:34 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/database/releases/tag/v3.2.9</guid>
	</item>
	<item>
		<title>Mail v4.1.0</title>
		<link>https://github.com/nette/mail/releases/tag/v4.1.0</link>
		<description>This release introduces CssInliner – a brand-new component that brings CSS-to-inline-style conversion directly into Nette Mail. The minimum PHP version has been raised to 8.2, and static analysis is now a mandatory part of the build pipeline.


Minimum PHP version raised from 8.0 to 8.2 – time to upgrade if you haven&apos;t already


Improved PHPDoc types and descriptions for better IDE support and static analysis accuracy


CssInliner – converts &lt;style&gt; rules into inline style attributes, making your HTML emails render consistently across email clients. Features a single-regex tokenizer, full CSS nesting support, Dom\HTMLDocument selector matching (PHP 8.4+), and automatic Outlook-compatible HTML attribute generation (bgcolor, width, align, etc.). &lt;style&gt; tags are preserved so @media queries keep working.

</description>
		<content:encoded><![CDATA[
		<p>This release introduces <strong>CssInliner</strong> – a brand-new component that brings CSS-to-inline-style conversion directly into Nette Mail. The minimum PHP version has been raised to 8.2, and static analysis is now a mandatory part of the build pipeline.</p>
<ul>
<li>
<p>Minimum PHP version raised from 8.0 to <strong>8.2</strong> – time to upgrade if you haven't already</p>
</li>
<li>
<p>Improved PHPDoc types and descriptions for better IDE support and static analysis accuracy</p>
</li>
<li>
<p><strong>CssInliner</strong> – converts <code>&lt;style&gt;</code> rules into inline <code>style</code> attributes, making your HTML emails render consistently across email clients. Features a single-regex tokenizer, full CSS nesting support, <code>Dom\HTMLDocument</code> selector matching (PHP 8.4+), and automatic Outlook-compatible HTML attribute generation (<code>bgcolor</code>, <code>width</code>, <code>align</code>, etc.). <code>&lt;style&gt;</code> tags are preserved so <code>@media</code> queries keep working.</p>
</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 27 Mar 2026 01:21:29 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/mail/releases/tag/v4.1.0</guid>
	</item>
	<item>
		<title>Latte v3.1.3</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.3</link>
		<description>
Feature::Dedent – once switched on, removes the structural indentation of paired tags from their content, so the generated HTML is indented as if the tags were not there
Feature::ScopedLoopVariables – once switched on, variables introduced by {foreach}, destructuring included, exist only inside the loop and do not overwrite variables of the same name outside it
|commas – joins items with a comma and optionally a different last glue: {$items|commas: &apos; and &apos;} gives a, b and c
|column – picks a single column of a list of arrays or objects, like array_column()
|limit – takes the first N items with their keys preserved: {$items|limit: 5}
|slice works with iterators too, not only arrays and strings
|padLeft and |padRight accept numbers (#408)
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Feature::Dedent</strong> – once switched on, removes the structural indentation of paired tags from their content, so the generated HTML is indented as if the tags were not there</li>
<li><strong>Feature::ScopedLoopVariables</strong> – once switched on, variables introduced by <code>{foreach}</code>, destructuring included, exist only inside the loop and do not overwrite variables of the same name outside it</li>
<li><strong>|commas</strong> – joins items with a comma and optionally a different last glue: <code>{$items|commas: ' and '}</code> gives <code>a, b and c</code></li>
<li><strong>|column</strong> – picks a single column of a list of arrays or objects, like <code>array_column()</code></li>
<li><strong>|limit</strong> – takes the first N items with their keys preserved: <code>{$items|limit: 5}</code></li>
<li><strong>|slice</strong> works with iterators too, not only arrays and strings</li>
<li><strong>|padLeft</strong> and <strong>|padRight</strong> accept numbers (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3995709642" data-permission-text="Title is private" data-url="https://github.com/nette/latte/issues/408" data-hovercard-type="issue" data-hovercard-url="/nette/latte/issues/408/hovercard" href="https://github.com/nette/latte/issues/408">#408</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 22 Mar 2026 23:05:54 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.3</guid>
	</item>
	<item>
		<title>Latte v3.1.2</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.2</link>
		<description>💥 Breaking Changes

TokenStream::peek() always returns a token and throws past the end of the stream; use the new tryPeek() where you expect null – only matters for custom tag parsers
A custom template function used with the first-class callable syntax myFunc(...) is a compile error
String filters such as |lower, |upper, |capitalize, |padLeft or |stripHtml and |replace got native types: they accept only strings (and Stringable), so passing an array raises a TypeError

✨ New Features

Feature enum with setFeature() and hasFeature() – one way to switch engine capabilities such as Feature::StrictTypes, Feature::StrictParsing or Feature::MigrationWarnings; the old setStrictTypes(), setStrictParsing() and setMigrationWarnings() still work but are deprecated
setCacheDirectory() replaces setTempDirectory(), which was too easy to mistake for a template directory; the old name still works

🐛 Bug Fixes

The linter reports an unknown class in {=Foo::class}
</description>
		<content:encoded><![CDATA[
		<h2>💥 Breaking Changes</h2>
<ul>
<li><strong>TokenStream::peek()</strong> always returns a token and throws past the end of the stream; use the new <strong>tryPeek()</strong> where you expect <code>null</code> – only matters for custom tag parsers</li>
<li>A custom template function used with the first-class callable syntax <code>myFunc(...)</code> is a compile error</li>
<li>String filters such as <code>|lower</code>, <code>|upper</code>, <code>|capitalize</code>, <code>|padLeft</code> or <code>|stripHtml</code> and <code>|replace</code> got native types: they accept only strings (and <code>Stringable</code>), so passing an array raises a <code>TypeError</code></li>
</ul>
<h2>✨ New Features</h2>
<ul>
<li><strong>Feature</strong> enum with <strong>setFeature()</strong> and <strong>hasFeature()</strong> – one way to switch engine capabilities such as <code>Feature::StrictTypes</code>, <code>Feature::StrictParsing</code> or <code>Feature::MigrationWarnings</code>; the old <code>setStrictTypes()</code>, <code>setStrictParsing()</code> and <code>setMigrationWarnings()</code> still work but are deprecated</li>
<li><strong>setCacheDirectory()</strong> replaces <code>setTempDirectory()</code>, which was too easy to mistake for a template directory; the old name still works</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li>The linter reports an unknown class in <code>{=Foo::class}</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 25 Feb 2026 01:37:42 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.2</guid>
	</item>
	<item>
		<title>Latte v3.0.26</title>
		<link>https://github.com/nette/latte/releases/tag/v3.0.26</link>
		<description>
Feature class with setFeature()/hasFeature() – a unified way to toggle engine capabilities. Existing methods like setStrictTypes() and setStrictParsing() now delegate to this system, so you can use either style. New features can be added without cluttering the Engine API.
setCacheDirectory() replaces the old setTempDirectory() – because &quot;temp&quot; was too easily confused with &quot;template&quot;. The old method still works but consider it deprecated.
Fixed ! operator priority – the logical NOT operator was incorrectly placed at the same precedence level as bitwise NOT and type casts, above instanceof. It now correctly sits below instanceof, matching PHP&apos;s actual operator precedence.
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Feature</strong> class with <strong>setFeature()</strong>/<strong>hasFeature()</strong> – a unified way to toggle engine capabilities. Existing methods like <code>setStrictTypes()</code> and <code>setStrictParsing()</code> now delegate to this system, so you can use either style. New features can be added without cluttering the Engine API.</li>
<li><strong>setCacheDirectory()</strong> replaces the old <code>setTempDirectory()</code> – because "temp" was too easily confused with "template". The old method still works but consider it deprecated.</li>
<li>Fixed <strong><code>!</code> operator priority</strong> – the logical NOT operator was incorrectly placed at the same precedence level as bitwise NOT and type casts, above <code>instanceof</code>. It now correctly sits below <code>instanceof</code>, matching PHP's actual operator precedence.</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 25 Feb 2026 00:02:23 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.0.26</guid>
	</item>
	<item>
		<title>Robot Loader v4.1.2</title>
		<link>https://github.com/nette/robot-loader/releases/tag/v4.1.2</link>
		<description>A code quality release that tightens static analysis and cleans up internals.

Fixed all PHPStan errors and improved phpDoc annotations
Switched to singleline declare statements across the codebase
</description>
		<content:encoded><![CDATA[
		<p>A code quality release that tightens static analysis and cleans up internals.</p>
<ul>
<li>Fixed all PHPStan errors and improved phpDoc annotations</li>
<li>Switched to singleline <code>declare</code> statements across the codebase</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 23 Feb 2026 04:21:58 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/robot-loader/releases/tag/v4.1.2</guid>
	</item>
	<item>
		<title>Routing v3.1.3</title>
		<link>https://github.com/nette/routing/releases/tag/v3.1.3</link>
		<description>A code quality release that tightens static analysis and cleans up internals.

Fixed all PHPStan errors and improved phpDoc annotations
Switched to singleline declare statements across the codebase
</description>
		<content:encoded><![CDATA[
		<p>A code quality release that tightens static analysis and cleans up internals.</p>
<ul>
<li>Fixed all PHPStan errors and improved phpDoc annotations</li>
<li>Switched to singleline <code>declare</code> statements across the codebase</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 23 Feb 2026 04:08:41 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/routing/releases/tag/v3.1.3</guid>
	</item>
	<item>
		<title>Schema v1.3.5</title>
		<link>https://github.com/nette/schema/releases/tag/v1.3.5</link>
		<description>A code quality release that tightens static analysis and cleans up internals.

Fixed all PHPStan errors and improved phpDoc annotations
Switched to singleline declare statements across the codebase
</description>
		<content:encoded><![CDATA[
		<p>A code quality release that tightens static analysis and cleans up internals.</p>
<ul>
<li>Fixed all PHPStan errors and improved phpDoc annotations</li>
<li>Switched to singleline <code>declare</code> statements across the codebase</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 23 Feb 2026 03:41:05 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/schema/releases/tag/v1.3.5</guid>
	</item>
	<item>
		<title>Safe Stream v3.0.4</title>
		<link>https://github.com/nette/safe-stream/releases/tag/v3.0.4</link>
		<description>A code quality release that tightens static analysis and cleans up internals.

Fixed all PHPStan errors and improved phpDoc annotations
Switched to singleline declare statements across the codebase
</description>
		<content:encoded><![CDATA[
		<p>A code quality release that tightens static analysis and cleans up internals.</p>
<ul>
<li>Fixed all PHPStan errors and improved phpDoc annotations</li>
<li>Switched to singleline <code>declare</code> statements across the codebase</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 23 Feb 2026 03:34:56 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/safe-stream/releases/tag/v3.0.4</guid>
	</item>
	<item>
		<title>Tracy v2.11.3</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.11.3</link>
		<description>
Templates converted to Latte-like syntax, paving the way for a cleaner templating pipeline
Environment guards relocated from Debugger to the individual strategy classes, improving separation of concerns
Upgraded to PHPStan level 8 — the strictest static analysis level is now passing
</description>
		<content:encoded><![CDATA[
		<ul>
<li><strong>Templates converted</strong> to Latte-like syntax, paving the way for a cleaner templating pipeline</li>
<li><strong>Environment guards</strong> relocated from <code>Debugger</code> to the individual strategy classes, improving separation of concerns</li>
<li>Upgraded to <strong>PHPStan level 8</strong> — the strictest static analysis level is now passing</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 20 Feb 2026 06:33:42 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.11.3</guid>
	</item>
	<item>
		<title>Utils v4.1.3</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.3</link>
		<description>A maintenance release focused on code quality: stricter types, better PHPDoc annotations, and PHPStan now runs as a mandatory CI check. No breaking changes.</description>
		<content:encoded><![CDATA[
		<p>A maintenance release focused on code quality: stricter types, better PHPDoc annotations, and PHPStan now runs as a mandatory CI check. No breaking changes.</p>
		]]></content:encoded>
		<pubDate>Fri, 13 Feb 2026 03:08:55 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.3</guid>
	</item>
	<item>
		<title>Php Generator v4.2.2</title>
		<link>https://github.com/nette/php-generator/releases/tag/v4.2.2</link>
		<description>This release focuses on making namespaces and classes work together more naturally. Classes now know which namespace they belong to, constructors accept fully qualified names, and a new unified add() method on PhpFile ties it all together. Under the hood, the Factory got a thorough refactoring and the codebase passed its first mandatory static analysis check.


PhpNamespace::add() now automatically assigns itself as the namespace of any ClassLike passed to it. If your code relied on getNamespace() returning null after adding a class to a namespace, you&apos;ll need to update that assumption.


PhpFile::add() – a single entry point for adding classes, interfaces, traits, enums, functions, and namespaces to a file. It handles namespace creation and bracket syntax automatically, so you can build a complete file with just add() calls.


ClassLike::getFullName() – returns the fully qualified name when the class belongs to a namespace (e.g., App\Model\User), the short name otherwise, or null for anonymous classes.


ClassLike constructors now accept FQN – pass &apos;App\Model\User&apos; and the namespace is extracted automatically. No need to create the namespace separately for simple cases.


PhpNamespace::add() accepts GlobalFunction – the unified add() method now handles functions alongside class-like types, making the namespace API more consistent.


The $namespace parameter in ClassLike constructors is deprecated. Use setNamespace() instead. The old signature still works for now, but will be removed in a future version.

</description>
		<content:encoded><![CDATA[
		<p>This release focuses on making namespaces and classes work together more naturally. Classes now know which namespace they belong to, constructors accept fully qualified names, and a new unified <code>add()</code> method on PhpFile ties it all together. Under the hood, the Factory got a thorough refactoring and the codebase passed its first mandatory static analysis check.</p>
<ul>
<li>
<p><strong>PhpNamespace::add()</strong> now automatically assigns itself as the namespace of any ClassLike passed to it. If your code relied on <code>getNamespace()</code> returning <code>null</code> after adding a class to a namespace, you'll need to update that assumption.</p>
</li>
<li>
<p><strong>PhpFile::add()</strong> – a single entry point for adding classes, interfaces, traits, enums, functions, and namespaces to a file. It handles namespace creation and bracket syntax automatically, so you can build a complete file with just <code>add()</code> calls.</p>
</li>
<li>
<p><strong>ClassLike::getFullName()</strong> – returns the fully qualified name when the class belongs to a namespace (e.g., <code>App\Model\User</code>), the short name otherwise, or <code>null</code> for anonymous classes.</p>
</li>
<li>
<p><strong>ClassLike constructors now accept FQN</strong> – pass <code>'App\Model\User'</code> and the namespace is extracted automatically. No need to create the namespace separately for simple cases.</p>
</li>
<li>
<p><strong>PhpNamespace::add() accepts GlobalFunction</strong> – the unified <code>add()</code> method now handles functions alongside class-like types, making the namespace API more consistent.</p>
</li>
<li>
<p>The <strong><code>$namespace</code> parameter in ClassLike constructors</strong> is deprecated. Use <code>setNamespace()</code> instead. The old signature still works for now, but will be removed in a future version.</p>
</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 09 Feb 2026 05:49:00 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/php-generator/releases/tag/v4.2.2</guid>
	</item>
	<item>
		<title>Tracy v2.11.1</title>
		<link>https://github.com/nette/tracy/releases/tag/v2.11.1</link>
		<description>✨ New Features

Dumper – added support for uninitialized lazy objects (PHP 8.4), displaying them with a (lazy) label and showing only pre-initialized properties
Source mapper – added column support, so BlueScreen can now pinpoint the exact character position in mapped source files

🐛 Bug Fixes

keysToHide now applies to bdump()/barDump() as well – previously sensitive keys were only hidden in dump() and BlueScreen (#608)
TracyExtension sets keysToHide config for Debugger too, not just for BlueScreen (#608)
Dumper correctly loads its assets even when $showBar = false (#606)
</description>
		<content:encoded><![CDATA[
		<h2>✨ New Features</h2>
<ul>
<li><strong>Dumper</strong> – added support for uninitialized lazy objects (PHP 8.4), displaying them with a <code>(lazy)</code> label and showing only pre-initialized properties</li>
<li><strong>Source mapper</strong> – added column support, so BlueScreen can now pinpoint the exact character position in mapped source files</li>
</ul>
<h2>🐛 Bug Fixes</h2>
<ul>
<li><strong><code>keysToHide</code></strong> now applies to <code>bdump()</code>/<code>barDump()</code> as well – previously sensitive keys were only hidden in <code>dump()</code> and BlueScreen (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3748993186" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/608" data-hovercard-type="issue" data-hovercard-url="/nette/tracy/issues/608/hovercard" href="https://github.com/nette/tracy/issues/608">#608</a>)</li>
<li><strong>TracyExtension</strong> sets <code>keysToHide</code> config for Debugger too, not just for BlueScreen (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3748993186" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/608" data-hovercard-type="issue" data-hovercard-url="/nette/tracy/issues/608/hovercard" href="https://github.com/nette/tracy/issues/608">#608</a>)</li>
<li><strong>Dumper</strong> correctly loads its assets even when <code>$showBar = false</code> (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3509985417" data-permission-text="Title is private" data-url="https://github.com/nette/tracy/issues/606" data-hovercard-type="issue" data-hovercard-url="/nette/tracy/issues/606/hovercard" href="https://github.com/nette/tracy/issues/606">#606</a>)</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 08 Feb 2026 01:13:23 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tracy/releases/tag/v2.11.1</guid>
	</item>
	<item>
		<title>Tester v2.6.0</title>
		<link>https://github.com/nette/tester/releases/tag/v2.6.0</link>
		<description>This release brings true parallel test execution on Windows, smarter PHP configuration handling, and a bunch of quality-of-life improvements. The headline: Tester now respects your system php.ini by default, which is a breaking change but makes the &quot;it works on my machine&quot; debugging sessions a lot shorter.
Breaking Changes

Tester now uses system php.ini by default (#465)

Improvements

Parallel execution on Windows finally works properly – PHP 8.5&apos;s stream_select() fix means Windows users can now enjoy actual parallelism, not just the illusion of it.
Fixed output loss on fast-exiting processes – A race condition could swallow test output when processes finished too quickly. Your test results now survive speed.

New Features

test() and testException() lifecycle improvements – Both functions now properly call setUp() and tearDown(), and tearDown() runs even when tests fail. Your cleanup code will actually clean up.
Added global function testNoError()
</description>
		<content:encoded><![CDATA[
		<p>This release brings true parallel test execution on Windows, smarter PHP configuration handling, and a bunch of quality-of-life improvements. The headline: Tester now respects your system php.ini by default, which is a breaking change but makes the "it works on my machine" debugging sessions a lot shorter.</p>
<h2>Breaking Changes</h2>
<ul>
<li>Tester now uses system <code>php.ini</code> by default (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3784290198" data-permission-text="Title is private" data-url="https://github.com/nette/tester/issues/465" data-hovercard-type="issue" data-hovercard-url="/nette/tester/issues/465/hovercard" href="https://github.com/nette/tester/issues/465">#465</a>)</li>
</ul>
<h2>Improvements</h2>
<ul>
<li>Parallel execution on Windows finally works properly – PHP 8.5's <code>stream_select()</code> fix means Windows users can now enjoy actual parallelism, not just the illusion of it.</li>
<li>Fixed output loss on fast-exiting processes – A race condition could swallow test output when processes finished too quickly. Your test results now survive speed.</li>
</ul>
<h2>New Features</h2>
<ul>
<li><code>test()</code> and <code>testException()</code> lifecycle improvements – Both functions now properly call <code>setUp()</code> and <code>tearDown()</code>, and <code>tearDown()</code> runs even when tests fail. Your cleanup code will actually clean up.</li>
<li>Added global function <code>testNoError()</code></li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 22 Jan 2026 06:49:06 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/tester/releases/tag/v2.6.0</guid>
	</item>
	<item>
		<title>Neon v3.4.7</title>
		<link>https://github.com/nette/neon/releases/tag/v3.4.7</link>
		<description>
Encoder: invalid UTF-8 sequences are replaced with U+FFFD  #76
improved neon-lint
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Encoder: invalid UTF-8 sequences are replaced with U+FFFD  <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="2872967568" data-permission-text="Title is private" data-url="https://github.com/nette/neon/issues/76" data-hovercard-type="issue" data-hovercard-url="/nette/neon/issues/76/hovercard" href="https://github.com/nette/neon/issues/76">#76</a></li>
<li>improved neon-lint</li>
</ul>
		]]></content:encoded>
		<pubDate>Sun, 04 Jan 2026 08:43:41 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v3.4.7</guid>
	</item>
	<item>
		<title>Utils v4.1.1</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.1</link>
		<description>
Html::addText() accepts int|null for back compatibility [Closes #332][Closes #333]
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Html::addText() accepts int|null for back compatibility [Closes <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3695264020" data-permission-text="Title is private" data-url="https://github.com/nette/utils/issues/332" data-hovercard-type="issue" data-hovercard-url="/nette/utils/issues/332/hovercard" href="https://github.com/nette/utils/issues/332">#332</a>][Closes <a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3698284841" data-permission-text="Title is private" data-url="https://github.com/nette/utils/issues/333" data-hovercard-type="pull_request" data-hovercard-url="/nette/utils/pull/333/hovercard" href="https://github.com/nette/utils/pull/333">#333</a>]</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 22 Dec 2025 12:08:17 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.1</guid>
	</item>
	<item>
		<title>Application v3.2.9</title>
		<link>https://github.com/nette/application/releases/tag/v3.2.9</link>
		<description>
added #[TemplateVariable]
LinkGenerator: throws an error when the link points to #[Requires(forward: true)]
</description>
		<content:encoded><![CDATA[
		<ul>
<li>added #[TemplateVariable]</li>
<li>LinkGenerator: throws an error when the link points to #[Requires(forward: true)]</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 19 Dec 2025 11:40:30 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/application/releases/tag/v3.2.9</guid>
	</item>
	<item>
		<title>Latte v3.1.1</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.1</link>
		<description>
added LinterExtension for validating filters, functions, classes and methods
linter: improved finding files, excludes temp, vendor, node_modules
support every argument syntax for clone() in PHP 8.5
added CustomFunctionCallNode for custom functions
refactor: decentralize operator precedence to individual nodes
*CallableNode replaced with solution with VariadicPlaceholder (BC break)
ErrorSuppressNode &amp; NotNode merged into UnaryOpNode (BC break)
deprecated PrintContext::infixOp(), prefixOp(), postfixOp() (BC break)
fixed operator ! priority
</description>
		<content:encoded><![CDATA[
		<ul>
<li>added LinterExtension for validating filters, functions, classes and methods</li>
<li>linter: improved finding files, excludes temp, vendor, node_modules</li>
<li>support every argument syntax for <code>clone()</code> in PHP 8.5</li>
<li>added CustomFunctionCallNode for custom functions</li>
<li>refactor: decentralize operator precedence to individual nodes</li>
<li>*CallableNode replaced with solution with VariadicPlaceholder (BC break)</li>
<li>ErrorSuppressNode &amp; NotNode merged into UnaryOpNode (BC break)</li>
<li>deprecated <code>PrintContext::infixOp()</code>, <code>prefixOp()</code>, <code>postfixOp()</code> (BC break)</li>
<li>fixed operator ! priority</li>
</ul>
		]]></content:encoded>
		<pubDate>Thu, 18 Dec 2025 22:42:28 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.1</guid>
	</item>
	<item>
		<title>Utils v4.1.0</title>
		<link>https://github.com/nette/utils/releases/tag/v4.1.0</link>
		<description>
requires PHP 8.2
DateTime: strict behavior (BC break)
Strings::webalize() requires INTL extension
StaticClass: is not overriding __callStatic()
</description>
		<content:encoded><![CDATA[
		<ul>
<li>requires PHP 8.2</li>
<li>DateTime: strict behavior (BC break)</li>
<li>Strings::webalize() requires INTL extension</li>
<li>StaticClass: is not overriding __callStatic()</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 01 Dec 2025 17:45:58 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.1.0</guid>
	</item>
	<item>
		<title>Utils v4.0.10</title>
		<link>https://github.com/nette/utils/releases/tag/v4.0.10</link>
		<description>
added Type::with()
added Type::fromValue()
added Helpers::splitClassName()
added Iterables::repeatable()
Finder: is_file() does not work with symlinks under Windows
</description>
		<content:encoded><![CDATA[
		<ul>
<li>added <code>Type::with()</code></li>
<li>added <code>Type::fromValue()</code></li>
<li>added <code>Helpers::splitClassName()</code></li>
<li>added <code>Iterables::repeatable()</code></li>
<li>Finder: <code>is_file()</code> does not work with symlinks under Windows</li>
</ul>
		]]></content:encoded>
		<pubDate>Mon, 01 Dec 2025 17:45:08 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/utils/releases/tag/v4.0.10</guid>
	</item>
	<item>
		<title>Latte v3.0.25</title>
		<link>https://github.com/nette/latte/releases/tag/v3.0.25</link>
		<description>
Escaper: supports converting HTML =&gt; TEXT
Escaper: fixed converting between HTML/ATTR &lt;=&gt; HTML
added ModifierNode::removeFilter()
linter: added assets extension
</description>
		<content:encoded><![CDATA[
		<ul>
<li>Escaper: supports converting HTML =&gt; TEXT</li>
<li>Escaper: fixed converting between HTML/ATTR <code>&lt;=&gt;</code> HTML</li>
<li>added <code>ModifierNode::removeFilter()</code></li>
<li>linter: added assets extension</li>
</ul>
		]]></content:encoded>
		<pubDate>Fri, 28 Nov 2025 17:39:12 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.0.25</guid>
	</item>
	<item>
		<title>Latte v3.1.0</title>
		<link>https://github.com/nette/latte/releases/tag/v3.1.0</link>
		<description>This major release introduces Smart HTML Attributes, strict_types by default, and several syntax improvements. It requires PHP 8.2+.
Smart HTML Attributes

Null values: Attributes with null values are now dropped instead of rendering as empty strings.
Boolean attributes: Attributes like checked or disabled render conditionally based on truthy/falsey values.
Array support: class and style attributes now accept arrays (e.g., class=&quot;{[active: $cond]}&quot;).
Data attributes: data-* attributes automatically JSON-serialize non-string values (arrays, objects, booleans).
Aria attributes: aria-* attributes render boolean values as &quot;true&quot;/&quot;false&quot;.
Type checking: Passing invalid types (arrays, objects) to standard attributes now triggers a warning and omits the attribute.

New Features

Added n:elseif support.
Added nullsafe filter operator ?| (e.g., {$var?|upper}).
Added |toggle filter for manual boolean attribute control.
Support for unquoted n-attribute syntax: n:if={$cond}.

Breaking Changes &amp; Deprecations

strictTypes is now enabled by default.
Using $this and $__* variables in templates is deprecated.
The undefined unsafe operator ??-&gt; is deprecated (use ?-&gt;).
Global constants should now be prefixed with a slash (e.g., \PHP_VERSION).
Engine::addFilterLoader() is deprecated.
</description>
		<content:encoded><![CDATA[
		<p>This major release introduces Smart HTML Attributes, <code>strict_types</code> by default, and several syntax improvements. It requires PHP 8.2+.</p>
<p><strong>Smart HTML Attributes</strong></p>
<ul>
<li><strong>Null values:</strong> Attributes with <code>null</code> values are now dropped instead of rendering as empty strings.</li>
<li><strong>Boolean attributes:</strong> Attributes like <code>checked</code> or <code>disabled</code> render conditionally based on truthy/falsey values.</li>
<li><strong>Array support:</strong> <code>class</code> and <code>style</code> attributes now accept arrays (e.g., <code>class="{[active: $cond]}"</code>).</li>
<li><strong>Data attributes:</strong> <code>data-*</code> attributes automatically JSON-serialize non-string values (arrays, objects, booleans).</li>
<li><strong>Aria attributes:</strong> <code>aria-*</code> attributes render boolean values as <code>"true"</code>/<code>"false"</code>.</li>
<li><strong>Type checking:</strong> Passing invalid types (arrays, objects) to standard attributes now triggers a warning and omits the attribute.</li>
</ul>
<p><strong>New Features</strong></p>
<ul>
<li>Added <code>n:elseif</code> support.</li>
<li>Added nullsafe filter operator <code>?|</code> (e.g., <code>{$var?|upper}</code>).</li>
<li>Added <code>|toggle</code> filter for manual boolean attribute control.</li>
<li>Support for unquoted n-attribute syntax: <code>n:if={$cond}</code>.</li>
</ul>
<p><strong>Breaking Changes &amp; Deprecations</strong></p>
<ul>
<li><code>strictTypes</code> is now enabled by default.</li>
<li>Using <code>$this</code> and <code>$__*</code> variables in templates is deprecated.</li>
<li>The undefined unsafe operator <code>??-&gt;</code> is deprecated (use <code>?-&gt;</code>).</li>
<li>Global constants should now be prefixed with a slash (e.g., <code>\PHP_VERSION</code>).</li>
<li><code>Engine::addFilterLoader()</code> is deprecated.</li>
</ul>
		]]></content:encoded>
		<pubDate>Wed, 26 Nov 2025 18:46:40 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/latte/releases/tag/v3.1.0</guid>
	</item>
	<item>
		<title>Neon v3.4.6</title>
		<link>https://github.com/nette/neon/releases/tag/v3.4.6</link>
		<description>
fixed mixed indents in block strings (#78)
Nodes: removes null nodes after traversal
adjusted exception message
</description>
		<content:encoded><![CDATA[
		<ul>
<li>fixed mixed indents in block strings (<a target=_blank rel=noopener class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="3159453298" data-permission-text="Title is private" data-url="https://github.com/nette/neon/issues/78" data-hovercard-type="pull_request" data-hovercard-url="/nette/neon/pull/78/hovercard" href="https://github.com/nette/neon/pull/78">#78</a>)</li>
<li>Nodes: removes null nodes after traversal</li>
<li>adjusted exception message</li>
</ul>
		]]></content:encoded>
		<pubDate>Tue, 25 Nov 2025 13:13:55 +0000</pubDate>
		<guid isPermaLink="true">https://github.com/nette/neon/releases/tag/v3.4.6</guid>
	</item>
</channel>
</rss>
