New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(host-rules): support matchHost with a dot prefix #11523
Conversation
Do you mean that we ended up with a "double dot" prefix when you first tried it? |
Exactly! I (incorrectly) configured ".docker.io" and renovate/lib/util/host-rules.ts Line 88 in b8e36da
|
We could/should probably fix that though |
Sounds good to me! Something like Would we still want to have clarification in the docs that this happens? Happy to PR this, with guidance on the desired approach. Also thanks for your time as always! |
I think that logic change sounds good. You're welcome to expand the explanation in the documentation too at the same time! |
@rarkins Updated! Please let me know what you think, at your convenience |
🎉 This PR is included in version 26.18.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
host-rules
will no longer double up on dot prefixes if the configured value ofmatchHost
already contains one.
Context:
I found myself wishing the docs called this out when I added my own dot prefix out of what
I thought was an abundance of caution, and inadvertently made it impossible to match any
hostnames due to the one already there :) Hoping to help clarify this for posterity.
Open to suggestions on the wording! I'm not sure I phrased this as clearly as possible or
kept the voice of the docs consistently.
Edit: updated per recommendation below to correct the behavior, in addition to clarifying
in the docs.
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: