Change rajentrivedi/tokenizer-x dependency back to release instead of specific commit once new release is made
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3462390. -->
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/3462385" title="Status: Closed (fixed)">#3462385: Fix composer.json compatibility with Drupal 10.2 - 11.x</a></span> we had to lock to a specific commit due to lack of release.<br>
Once <a href="https://github.com/rajentrivedi/tokenizer-x">https://github.com/rajentrivedi/tokenizer-x</a> has a new release, we can lock back to a release</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p>Check composer.json</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Lock back to release once its made</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>Update composer.json back</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