Fix: allow dots in bucket name#1150
Merged
mpnowacki-reef merged 1 commit intoJun 8, 2026
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
According to official documentation bucket names should allow dots (
.). This PR adds dot to a list of allowed characters.It's also important to mention that the current CLI implementation only restricts bucket name characters to [a-z0-9.-], while the actual rules are more restrictive (for example, bucket names cannot start or end with a dot or contain consecutive dots). However, we don't enforce any additional naming rules at the CLI level and instead allow the B2 API to perform the validation and return an error. This way, the bucket name rules are always up-to-date, and we don't need to update the CLI if the rules change on the API side.