chore(release): bump versions and update changelogs#102
Merged
Conversation
garrensmith
approved these changes
May 11, 2026
designcode
approved these changes
May 11, 2026
Greptile SummaryThis is an automated Changesets release PR that bumps
Confidence Score: 5/5Safe to merge — all three changed files are version metadata and changelog prose generated by the Changesets action with no logic changes. The diff touches only package.json (version bump), CHANGELOG.md (new release entry), and the deletion of the consumed changeset file. There is no source code change introduced by this PR itself. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "chore(release): bump versions and update..." | Re-trigger Greptile |
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tigrisdata/storage@3.5.2
Patch Changes
#101
6306356Thanks @designcode! - Fix403 SignatureDoesNotMatchfromcopy,move, andupdateObjectwhen the object key contains/or any other character that requires percent-encoding (space,?,=, etc.) and the request is signed with access-key SigV4.Two related fixes:
SignatureV4withuriEscapePath: false, matching S3's single-encoding canonical-path scheme. The defaulttrue(AWS-standard double-encoding) caused the signer to re-escape any percent sequence in the path during canonicalization, while Tigris gateway uses S3 single-encoding — producing the mismatch for every key with a special char.X-Amz-Copy-Sourceheader are URL-encoded per-segment via the newencodeObjectKeyhelper, preserving/as a separator so the wire URL stays valid.OAuth/session-token callers were unaffected because that auth path skips SigV4 signing entirely.