Remove composer require of dev release of Key module when Key makes a new release
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3501028. -->
Reported by: [scott_euser](https://www.drupal.org/user/3267594)
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>In <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/ai/issues/3495702" title="Status: Closed (fixed)">#3495702: Add AI Search basic functional test coverage</a></span> we added test coverage for AI Search, but that flags deprecations for the Key module which are fixed here <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/key/issues/3489100" title="Status: Closed (fixed)">#3489100: Fix deprecations for PHP 8.4</a></span>. We need to remain locked to stable release of Key in our composer dependencies, so gitlab-ci.yaml updates to the dev version within phpunit next major</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p>Check gitlab-ci.yaml in project root</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Once Key module has a new release in 2025 we can remove the comment and corresponding code at <a href="https://git.drupalcode.org/project/ai/-/blob/1.0.x/.gitlab-ci.yml?ref_type=heads#L74">https://git.drupalcode.org/project/ai/-/blob/1.0.x/.gitlab-ci.yml?ref_type=heads#L74</a></p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>Remove comment and composer require when Key has a release</p>
<h3 id="summary-ui-changes">User interface changes</h3>
<p>N/A</p>
<h3 id="summary-api-changes">API changes</h3>
<p>N/A</p>
<h3 id="summary-data-model-changes">Data model changes</h3>
<p>N/A</p>
issue