github-actions[bot] commented on PR #5375:
URL: https://github.com/apache/solr/pull/5375#issuecomment-7071451318

   **Automated PR readiness judgements** (LLM-generated; may be wrong; not 
updated on later pushes).
   
   ⚠️ Prefer PRs against `main`. This PR targets branch_10x.
   
   - ✅ [Jira issue in 
title](https://github.com/apache/solr/blob/main/CONTRIBUTING.md): already 
present
   - ✅ 
[Changelog](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc#_changelog_types_reference):
 type: fixed <!-- The change fixes a bug where DELETEREPLICA by count failed 
with &#39;Could not find collection&#39; when the collection was an alias and 
followAliases was true&#44; which is a user&#45;visible error&#46;​ -->
   - ✅ [Reference Guide 
update](https://github.com/apache/solr/tree/main/solr/solr-ref-guide): not 
needed <!-- The PR fixes a bug in the existing behavior of the followAliases 
parameter for the DELETEREPLICA command&#59; it does not introduce new 
parameters or change the documented contract&#44; so no reference guide update 
is required&#46;​ -->
   - ✅ [Upgrade 
notes](https://github.com/apache/solr/tree/main/solr/solr-ref-guide/modules/upgrade-notes/pages):
 not needed <!-- This is a bug fix that makes the command work as expected when 
followAliases is true&#59; it is not a backwards&#45;incompatible change&#46;​ 
-->
   - ✅ Tests: included <!-- The PR modifies production logic in 
DeleteReplicaCmd&#46;​java to handle alias resolution&#44; which warrants new 
or updated tests to verify the fix&#46;​ -->
   
   <!-- Assessed commit 88d40918cb016bea72dba0fbee0513b504e407b3 -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to