Bumps [botocore](https://github.com/boto/botocore) from 1.32.7 to
1.42.59.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="c204bb1da1"><code>c204bb1</code></a>
Merge branch 'release-1.42.59'</li>
<li><a
href="7e59865407"><code>7e59865</code></a>
Bumping version to 1.42.59</li>
<li><a
href="b38a03ce4d"><code>b38a03c</code></a>
Update to latest models</li>
<li><a
href="97336ff38f"><code>97336ff</code></a>
Merge customizations for ARC Region switch</li>
<li><a
href="f76046b4bd"><code>f76046b</code></a>
Merge branch 'release-1.42.58'</li>
<li><a
href="be2689a1ee"><code>be2689a</code></a>
Merge branch 'release-1.42.58' into develop</li>
<li><a
href="47f8789f55"><code>47f8789</code></a>
Bumping version to 1.42.58</li>
<li><a
href="14bc74f6f6"><code>14bc74f</code></a>
Update to latest models</li>
<li><a
href="8c0427aaab"><code>8c0427a</code></a>
Add support for None values in list parsing (<a
href="https://redirect.github.com/boto/botocore/issues/3618">#3618</a>)</li>
<li><a
href="86d9ec3b0f"><code>86d9ec3</code></a>
Merge branch 'release-1.42.57'</li>
<li>Additional commits viewable in <a
href="https://github.com/boto/botocore/compare/1.32.7...1.42.59">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Bumps
[email-validator](https://github.com/JoshData/python-email-validator)
from 2.1.0.post1 to 2.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/JoshData/python-email-validator/releases">email-validator's
releases</a>.</em></p>
<blockquote>
<h2>v2.3.0</h2>
<ul>
<li>The package name is changed from using an underscore
(email_validator) to a dash (email-validator) to match PyPi's normalized
package name.</li>
<li>The library no longer checks that the local part is at most 64
characters because a more careful reading of RFC 5321 indicates the
limit is optional and such email addresses have been found in the wild.
However the check can be restored using a new <code>strict=True</code>
parameter, and the overall 254 character email address length limit is
still in place.</li>
<li>New EmailSyntaxError messages are used for some exiting syntax
errors related to @-sign homoglyphs and invalid characters in
internationalized domains.</li>
<li>When using <code>allow_display_name=True</code>, display names are
now returned with Unicode NFC normalization.</li>
<li>TypeError is now raised if something other than str (or bytes) is
passed as the email address.</li>
</ul>
<h2>2.2.0 (June 20, 2024)</h2>
<ul>
<li>Email addresses with internationalized local parts could, with rare
Unicode characters, be returned as valid but actually be invalid in
their normalized form (returned in the <code>normalized</code> field).
Local parts now re-validated after Unicode NFC normalization to ensure
that invalid characters cannot be injected into the normalized address
and that characters with length-increasing NFC normalizations cannot
cause a local part to exceed the maximum length after
normalization.</li>
<li>The length check for email addresses with internationalized local
parts is now also applied to the original address string prior to
Unicode NFC normalization, which may be longer and could exceed the
maximum email address length, to protect callers who do not use the
returned normalized address.</li>
<li>Improved error message for IDNA domains that are too long or have
invalid characters after Unicode normalization.</li>
<li>A new option to parse <code>My Name <address@domain></code>
strings, i.e. a display name plus an email address in angle brackets, is
now available. It is off by default.</li>
<li>Improvements to Python typing.</li>
<li>Some additional tests added.</li>
</ul>
<h2>v2.1.2</h2>
<h2>2.1.2 (June 16, 2024)</h2>
<ul>
<li>The domain name length limit is corrected from 255 to 253 IDNA ASCII
characters. I misread the RFCs.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, if none of the IP addresses in the response are globally
reachable (i.e. not Private-Use, Loopback, etc.), the response is
treated as if there was no A/AAAA response and the email address will
fail the deliverability check.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, the mx field in the object returned by validate_email
incorrectly held the IP addresses rather than the domain itself.</li>
<li>Fixes in tests.</li>
</ul>
<h2>v2.1.1 (February 26, 2024)</h2>
<ul>
<li>Fixed typo 'marking' instead of 'marketing' in case-insensitive
mailbox name list.</li>
<li>When DNS-based deliverability checks fail, in some cases exceptions
are now thrown with <code>raise ... from</code> for better nested
exception tracking.</li>
<li>Fixed tests to work when no local resolver can be configured.</li>
<li>This project is now licensed under the Unlicense (instead of
CC0).</li>
<li>Minor improvements to tests.</li>
<li>Minor improvements to code style.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/JoshData/python-email-validator/blob/main/CHANGELOG.md">email-validator's
changelog</a>.</em></p>
<blockquote>
<h2>2.3.0 (August 26, 2025)</h2>
<ul>
<li>The package name is changed from using an underscore
(email_validator) to a dash (email-validator) to match PyPi's normalized
package name.</li>
<li>The library no longer checks that the local part is at most 64
characters because a more careful reading of RFC 5321 indicates the
limit is optional and such email addresses have been found in the wild.
However the check can be restored using a new <code>strict=True</code>
parameter, and the overall 254 character email address length limit is
still in place.</li>
<li>New EmailSyntaxError messages are used for some exiting syntax
errors related to @-sign homoglyphs and invalid characters in
internationalized domains.</li>
<li>When using <code>allow_display_name=True</code>, display names are
now returned with Unicode NFC normalization.</li>
<li>TypeError is now raised if something other than str (or bytes) is
passed as the email address.</li>
</ul>
<h2>2.2.0 (June 20, 2024)</h2>
<ul>
<li>Email addresses with internationalized local parts could, with rare
Unicode characters, be returned as valid but actually be invalid in
their normalized form (returned in the <code>normalized</code> field).
In particular, it is possible to get a normalized address with a
";" character, which is not valid and could change the
interpretation of the address. Local parts now re-validated after
Unicode NFC normalization to ensure that invalid characters cannot be
injected into the normalized address and that characters with
length-increasing NFC normalizations cannot cause a local part to exceed
the maximum length after normalization. Thanks to <a
href="mailto:khanh@calif.io">khanh@calif.io</a> from <a
href="https://calif.io">https://calif.io</a> for reporting the
issue.</li>
<li>The length check for email addresses with internationalized local
parts is now also applied to the original address string prior to
Unicode NFC normalization, which may be longer and could exceed the
maximum email address length, to protect callers who do not use the
returned normalized address.</li>
<li>Improved error message for IDNA domains that are too long or have
invalid characters after Unicode normalization.</li>
<li>A new option to parse <code>My Name <address@domain></code>
strings, i.e. a display name plus an email address in angle brackets, is
now available. It is off by default.</li>
<li>Improvements to Python typing.</li>
<li>Some additional tests added.</li>
</ul>
<h2>2.1.2 (June 16, 2024)</h2>
<ul>
<li>The domain name length limit is corrected from 255 to 253 IDNA ASCII
characters. I misread the RFCs.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, if none of the IP addresses in the response are globally
reachable (i.e. not Private-Use, Loopback, etc.), the response is
treated as if there was no A/AAAA response and the email address will
fail the deliverability check.</li>
<li>When a domain name has no MX record but does have an A or AAAA
record, the mx field in the object returned by validate_email
incorrectly held the IP addresses rather than the domain itself.</li>
<li>Fixes in tests.</li>
</ul>
<h2>2.1.1 (February 26, 2024)</h2>
<ul>
<li>Fixed typo 'marking' instead of 'marketing' in case-insensitive
mailbox name list.</li>
<li>When DNS-based deliverability checks fail, in some cases exceptions
are now thrown with <code>raise ... from</code> for better nested
exception tracking.</li>
<li>Fixed tests to work when no local resolver can be configured.</li>
<li>This project is now licensed under the Unlicense (instead of
CC0).</li>
<li>Minor improvements to tests.</li>
<li>Minor improvements to code style.</li>
</ul>
<h2>2.1.0 (October 22, 2023)</h2>
<ul>
<li>Python 3.8+ is now required (support for Python 3.7 was
dropped).</li>
<li>The old <code>email</code> field on the returned
<code>ValidatedEmail</code> object, which in the previous version was
superseded by <code>normalized</code>, will now raise a deprecation
warning if used. See <a
href="https://stackoverflow.com/q/879173">https://stackoverflow.com/q/879173</a>
for strategies to suppress the DeprecationWarning.</li>
<li>A <code>__version__</code> module attribute is added.</li>
<li>The email address argument to validate_email is now marked as
positional-only to better reflect the documented usage using the new
Python 3.8 feature.</li>
</ul>
<h2>2.0.0 (April 15, 2023)</h2>
<p>This is a major update to the library, but since email address specs
haven't changed there should be no significant changes to which email
addresses are considered valid or invalid with default options. There
are new options for accepting unusual email addresses that were
previously always rejected, some changes to how DNS errors are handled,
many changes in error message text, and major internal improvements
including the addition of type annotations. Python 3.7+ is now required.
Details follow:</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/JoshData/python-email-validator/commits/v2.3.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Bumps [psycopg2-binary](https://github.com/psycopg/psycopg2) from 2.9.9
to 2.9.11.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/psycopg/psycopg2/blob/master/NEWS">psycopg2-binary's
changelog</a>.</em></p>
<blockquote>
<h2>Current release</h2>
<p>What's new in psycopg 2.9.11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Add support for Python 3.14.</li>
<li>Avoid a segfault passing more arguments than placeholders if Python
is built
with assertions enabled
(🎫<code>[#1791](https://github.com/psycopg/psycopg2/issues/1791)</code>).</li>
<li>Add riscv64 platform binary packages
(🎫<code>[#1813](https://github.com/psycopg/psycopg2/issues/1813)</code>).</li>
<li><code>~psycopg2.errorcodes</code> map and
<code>~psycopg2.errors</code> classes updated to
PostgreSQL 18.</li>
<li>Drop support for Python 3.8.</li>
</ul>
<p>What's new in psycopg 2.9.10
^^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Add support for Python 3.13.</li>
<li>Receive notifications on commit
(🎫<code>[#1728](https://github.com/psycopg/psycopg2/issues/1728)</code>).</li>
<li><code>~psycopg2.errorcodes</code> map and
<code>~psycopg2.errors</code> classes updated to
PostgreSQL 17.</li>
<li>Drop support for Python 3.7.</li>
</ul>
<p>What's new in psycopg 2.9.9
^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Add support for Python 3.12.</li>
<li>Drop support for Python 3.6.</li>
</ul>
<p>What's new in psycopg 2.9.8
^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Wheel package bundled with PostgreSQL 16 libpq in order to add
support for
recent features, such as <code>sslcertmode</code>.</li>
</ul>
<p>What's new in psycopg 2.9.7
^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<ul>
<li>Fix propagation of exceptions raised during module initialization
(🎫<code>[#1598](https://github.com/psycopg/psycopg2/issues/1598)</code>).</li>
<li>Fix building when pg_config returns an empty string
(🎫<code>[#1599](https://github.com/psycopg/psycopg2/issues/1599)</code>).</li>
<li>Wheel package bundled with OpenSSL 1.1.1v.</li>
</ul>
<p>What's new in psycopg 2.9.6
^^^^^^^^^^^^^^^^^^^^^^^^^^^</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="fd9ae8cad2"><code>fd9ae8c</code></a>
chore: bump to version 2.9.11</li>
<li><a
href="d923840546"><code>d923840</code></a>
chore: update docs requirements</li>
<li><a
href="d42dc7169d"><code>d42dc71</code></a>
Merge branch 'fix-1791'</li>
<li><a
href="4fde6560c3"><code>4fde656</code></a>
fix: avoid failed assert passing more arguments than placeholders</li>
<li><a
href="8308c19d6a"><code>8308c19</code></a>
fix: drop warning about the use of deprecated PyWeakref_GetObject
function</li>
<li><a
href="1a1eabf098"><code>1a1eabf</code></a>
build(deps): bump actions/github-script from 7 to 8</li>
<li><a
href="897af8b38b"><code>897af8b</code></a>
build(deps): bump peter-evans/repository-dispatch from 3 to 4</li>
<li><a
href="ceefd30511"><code>ceefd30</code></a>
build(deps): bump actions/checkout from 4 to 5</li>
<li><a
href="4dc585430c"><code>4dc5854</code></a>
build(deps): bump actions/setup-python from 5 to 6</li>
<li><a
href="1945788dcf"><code>1945788</code></a>
Merge pull request <a
href="https://redirect.github.com/psycopg/psycopg2/issues/1802">#1802</a>
from edgarrmondragon/cp314-wheels</li>
<li>Additional commits viewable in <a
href="https://github.com/psycopg/psycopg2/compare/2.9.9...2.9.11">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Bumps
[hashlib-additional](https://github.com/rfinnie/python-hashlib-additional)
from 1.0.0 to 1.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/rfinnie/python-hashlib-additional/releases">hashlib-additional's
releases</a>.</em></p>
<blockquote>
<h2>hashlib-additional 1.1</h2>
<ul>
<li>Fix setup.py encoding issue on Windows</li>
<li>Add new checksums: cksum, sysv, fletcher16, fletcher32,
fletcher64</li>
<li>Additional build/CI/test improvements</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="42c209ed4b"><code>42c209e</code></a>
hashlib-additional 1.1</li>
<li><a
href="02f80b372e"><code>02f80b3</code></a>
Small fix, if -> elif</li>
<li><a
href="1ea6ae2d8f"><code>1ea6ae2</code></a>
Add Fletcher checksums</li>
<li><a
href="f38943cb7e"><code>f38943c</code></a>
Test Python 3.9</li>
<li><a
href="96a7e305d9"><code>96a7e30</code></a>
Enforce coverage</li>
<li><a
href="9682c93ccf"><code>9682c93</code></a>
Remove unneeded flake8 C901 ignore</li>
<li><a
href="baf2a07ddf"><code>baf2a07</code></a>
setup.py: force UTF-8 README for Windows</li>
<li><a
href="189ef49eb2"><code>189ef49</code></a>
100% code coverage</li>
<li><a
href="005805d2bc"><code>005805d</code></a>
Implement tox, CI</li>
<li><a
href="26523727ca"><code>2652372</code></a>
Doc updates</li>
<li>Additional commits viewable in <a
href="https://github.com/rfinnie/python-hashlib-additional/compare/v1.0...v1.1">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Bumps [psutil](https://github.com/giampaolo/psutil) from 5.9.6 to 7.2.2.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/giampaolo/psutil/blob/master/HISTORY.rst">psutil's
changelog</a>.</em></p>
<blockquote>
<h1>7.2.2</h1>
<p>2026-01-28</p>
<p><strong>Enhancements</strong></p>
<ul>
<li>2705_: [Linux]: <code>Process.wait()</code>_ now uses
<code>pidfd_open()</code> + <code>poll()</code> for
waiting, resulting in no busy loop and faster response times. Requires
Linux >= 5.3 and Python >= 3.9. Falls back to traditional polling
if
unavailable.</li>
<li>2705_: [macOS], [BSD]: <code>Process.wait()</code>_ now uses
<code>kqueue()</code> for waiting,
resulting in no busy loop and faster response times.</li>
</ul>
<p><strong>Bug fixes</strong></p>
<ul>
<li>2701_, [macOS]: fix compilation error on macOS < 10.7. (patch by
Sergey
Fedorov)</li>
<li>2707_, [macOS]: fix potential memory leaks in error paths of
<code>Process.memory_full_info()</code> and
<code>Process.threads()</code>.</li>
<li>2708_, [macOS]: Process.cmdline()<code>_ and
</code>Process.environ()<code>_ may fail with ``OSError: [Errno 0]
Undefined error`` (from ``sysctl(KERN_PROCARGS2)``). They now raise
</code>AccessDenied`_ instead.</li>
</ul>
<h1>7.2.1</h1>
<p>2025-12-29</p>
<p><strong>Bug fixes</strong></p>
<ul>
<li>2699_, [FreeBSD], [NetBSD]: <code>heap_info()</code>_ does not
detect small allocations
(<= 1K). In order to fix that, we now flush internal jemalloc cache
before
fetching the metrics.</li>
</ul>
<h1>7.2.0</h1>
<p>2025-12-23</p>
<p><strong>Enhancements</strong></p>
<ul>
<li>1275_: new <code>heap_info()</code>_ and <code>heap_trim()</code>_
functions, providing direct
access to the platform's native C heap allocator (glibc, mimalloc,
libmalloc). Useful to create tools to detect memory leaks.</li>
<li>2403_, [Linux]: publish wheels for Linux musl.</li>
<li>2680_: unit tests are no longer installed / part of the
distribution. They
now live under <code>tests/</code> instead of
<code>psutil/tests</code>.</li>
</ul>
<p><strong>Bug fixes</strong></p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="9eea97dd6f"><code>9eea97d</code></a>
Pre-release</li>
<li><a
href="938ac64741"><code>938ac64</code></a>
Rm sphinxcontrib.googleanalytics; override layout.html</li>
<li><a
href="9dcbb7e60e"><code>9dcbb7e</code></a>
Add sphinxcontrib-googleanalytics to requirements.txt</li>
<li><a
href="76eaf9ae0f"><code>76eaf9a</code></a>
Try to add google analytics to doc</li>
<li><a
href="de1cafa56f"><code>de1cafa</code></a>
Update doc mentioning Process.wait() internal details</li>
<li><a
href="bb30943b03"><code>bb30943</code></a>
Refact can_use_pidfd_open() and can_use_kqueue()</li>
<li><a
href="a571717d65"><code>a571717</code></a>
<a
href="https://redirect.github.com/giampaolo/psutil/issues/2708">#2708</a>,
macos / cmdline / environ; raise AD instead of OSError(0) (<a
href="https://redirect.github.com/giampaolo/psutil/issues/2709">#2709</a>)</li>
<li><a
href="8b98c3effc"><code>8b98c3e</code></a>
Pre-release</li>
<li><a
href="700b7e6a41"><code>700b7e6</code></a>
[macOS] fix potential leaks in error paths (<a
href="https://redirect.github.com/giampaolo/psutil/issues/2707">#2707</a>)</li>
<li><a
href="7cc7923a14"><code>7cc7923</code></a>
Windows / cmdline(): be more defensive in free()ing in case of
error</li>
<li>Additional commits viewable in <a
href="https://github.com/giampaolo/psutil/compare/release-5.9.6...release-7.2.2">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Add full window maximize support to the BlackRoad OS window manager:
- Toggle maximize with button click or double-click on titlebar
- Store original window bounds for proper restore behavior
- Update maximize button icon (□ → ❐) when maximized
- Prevent window dragging when maximized
- Emit window:maximized and window:unmaximized events
- Add comprehensive CSS styles for maximized state
- CSS styles are injected dynamically to ensure availability
This completes the v0.2.0 window maximize feature marked as TODO.
Update the BR-95 Edition with the official brand gradient colors:
- #FF9D00 (orange) → #FF6B00 (deep orange) → #FF0066 (hot pink)
- → #FF006B (magenta-pink) → #D600AA (magenta)
- → #7700FF (electric purple) → #0066FF (electric blue)
Applied across boot logo, menu bar, and taskbar road logo
for cohesive brand identity throughout the interface.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Updates:
- Add app.blackroad.systems to ALLOWED_ORIGINS in both .env.example and config.py
- Add blackroad-operating-system-production.up.railway.app to ALLOWED_ORIGINS
- Update DNS.md to reflect current domain routing (both root and app subdomains point to same service)
- Ensures CORS works correctly for all production domains
This fixes CORS issues when accessing the application via app.blackroad.systems or blackroad.systems
on the Railway project 'gregarious-wonder' (blackroad-operating-system-production service).
This implements the "Big Kahuna" master orchestration plan to get BlackRoad OS
fully online and deployable without manual PR management.
## Backend Service (blackroad-core)
- Add /version endpoint with build metadata
- Prism Console already mounted at /prism
- Health check at /health
- Comprehensive API health at /api/health/summary
## Operator Service (blackroad-operator)
- Add /version endpoint with build metadata
- Create requirements.txt for dependencies
- Create Dockerfile for containerization
- Create railway.toml for Railway deployment
- Health check at /health
## Infrastructure
- Consolidate railway.toml for monorepo multi-service deployment
- Backend service (Dockerfile-based)
- Operator service (Nixpacks-based)
- Remove conflicting railway.json
## Documentation
- Add DEPLOYMENT_SMOKE_TEST_GUIDE.md
- Complete deployment instructions (local + Railway)
- Automated smoke test suite
- Troubleshooting guide
- Monitoring & health check setup
- Add infra/DNS_CLOUDFLARE_PLAN.md
- Complete DNS record table
- Cloudflare configuration steps
- Health check configuration
- Security best practices
## Testing
- Add scripts/smoke-test.sh for automated endpoint testing
- Validates all health and version endpoints
- Supports both Railway and Cloudflare URLs
## Result
Alexa can now:
1. Push to main → GitHub Actions deploys to Railway
2. Configure Cloudflare DNS (one-time setup)
3. Run smoke tests to verify everything works
4. Visit https://os.blackroad.systems and use the OS
No manual PR merging, no config juggling, no infrastructure babysitting.
This commit integrates the LEITL (Live Everyone In The Loop) Protocol and
Cece Cognition Framework into the BlackRoad agent ecosystem, enabling
multi-agent collaboration and advanced reasoning capabilities.
**Changes:**
1. **Cognition Router Integration** (`backend/app/routers/cognition.py`):
- Fixed import path for orchestration service
- Exposes full Cece Cognition Framework via REST API
- Endpoints for single agent execution and multi-agent workflows
- Supports sequential, parallel, and recursive execution modes
2. **Main App Updates** (`backend/app/main.py`):
- Added cognition router to imports
- Registered `/api/cognition` endpoints
- Added Cognition tag to OpenAPI docs
3. **BaseAgent LEITL Integration** (`agents/base/agent.py`):
- Added optional LEITL protocol support to base agent class
- New methods: `enable_leitl()`, `disable_leitl()`, `_leitl_broadcast()`, `_leitl_heartbeat()`
- Automatic event broadcasting during agent execution lifecycle
- Events: task.started, task.completed, task.failed
- Heartbeat support for session keep-alive
4. **AgentRegistry LEITL Support** (`agents/base/registry.py`):
- Added `enable_leitl_for_all()` - Enable LEITL for all registered agents
- Added `disable_leitl_for_all()` - Disable LEITL for all agents
- Added `get_leitl_status()` - Get LEITL status and session IDs
- Bulk agent session management
**Integration Architecture:**
```
User Request → Cognition API (/api/cognition)
↓
Orchestration Engine
↓
┌────────────┴──────────┐
↓ ↓
Cece Agent Other Agents
(15-step reasoning) (specialized)
↓ ↓
LEITL Protocol (if enabled)
↓
Redis PubSub + WebSocket
↓
Other active sessions
```
**New Capabilities:**
1. **Single Agent Execution**: POST /api/cognition/execute
- Execute Cece, Wasp, Clause, or Codex individually
- Full reasoning trace and confidence scores
2. **Multi-Agent Workflows**: POST /api/cognition/workflows
- Orchestrate multiple agents in complex workflows
- Sequential, parallel, or recursive execution
- Shared memory and context across agents
3. **LEITL Collaboration**:
- All agents can now broadcast their activity in real-time
- Multi-agent sessions can see each other's work
- Live activity feed via WebSocket
- Session management with heartbeats
4. **Agent Registry**:
- Bulk enable/disable LEITL for all agents
- Query LEITL status across the agent ecosystem
- Centralized session management
**Testing:**
- ✅ All Python files compile successfully
- ✅ Orchestration engine imports correctly
- ✅ BaseAgent with LEITL integration works
- ✅ AgentRegistry with LEITL support works
- ✅ Cece agent imports and executes
Implements a complete vertical slice of the IP Vault feature for BlackRoad OS,
providing cryptographic timestamping and evidence generation for ideas and
intellectual property.
## Components Added
### Agent Layer
- **VaultAgent** (`agents/categories/security/vault_agent.py`):
- Deterministic text canonicalization
- Multi-hash generation (SHA-256, SHA-512, Keccak-256)
- LEO (Ledger Evidence Object) construction
- Verification text generation
- Blockchain anchoring preparation
### Backend API
- **Models** (`backend/app/models/leo.py`):
- LEO: Stores cryptographic hashes and metadata
- AnchorEvent: Audit trail for blockchain anchoring
- **Schemas** (`backend/app/schemas/leo.py`):
- LEOCreate, LEOResponse, LEODetail, LEOList
- AnchorRequest, AnchorEventResponse
- **Router** (`backend/app/routers/ip_vault.py`):
- POST /api/vault/leos - Create new LEO
- GET /api/vault/leos - List LEOs (paginated)
- GET /api/vault/leos/{id} - Get LEO details
- POST /api/vault/leos/{id}/anchor - Initiate anchoring (stub)
- GET /api/vault/leos/{id}/events - Get anchor events
### Frontend
- **API Client** (`backend/static/js/api-client.js`):
- createLEO(), getLEOs(), getLEO()
- anchorLEO(), getLEOEvents()
- **App** (`backend/static/js/apps.js`):
- loadIPVault() - Load and display LEOs
- vaultIdea() - Create new LEO from form
- viewLEO() - Show detailed LEO modal with verification
- **UI** (`backend/static/index.html`):
- Desktop icon (🔐 IP Vault)
- Window with form and list view
- Start menu integration
## Features
- **Deterministic canonicalization**: Ensures reproducible hashing
- **Multi-hash support**: SHA-256, SHA-512, Keccak-256 (Ethereum-compatible)
- **Verification instructions**: Auto-generated proof-of-authenticity text
- **Blockchain-ready**: Prepared for Bitcoin, Litecoin, Ethereum anchoring
- **Clean separation**: Agent logic, API, database, frontend all decoupled
## Testing
- Python syntax validated for all new files
- JavaScript syntax validated
- VaultAgent tested end-to-end with sample idea
- All hashes computed successfully
## Next Steps
- Implement actual blockchain anchoring
- Add RoadChain integration
- Export LEOs as legal-grade PDFs
- Add user authentication to LEO creation
