This repository was archived by the owner on Jan 23, 2026. It is now read-only.
Merged
Conversation
fenos
force-pushed
the
storage/optionally-use-new-hostname
branch
from
75b6ac2 to
c8eeba4
Compare
itslenny
approved these changes
Jul 8, 2025
Contributor
itslenny
left a comment
itslenny
left a comment
There was a problem hiding this comment.
I think this works. Later when we're sure this is working well we can change the default value to true to make the new host the default, and users can still pass false to disable it.
Member
|
🎉 This PR is included in version 2.10.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the new behavior?
Opt-in behaviour of using the new storage hostname