Skip to content
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(s3s/sig_v4): support sts signature #208

Merged
merged 2 commits into from
Oct 25, 2024
Merged

fix(s3s/sig_v4): support sts signature #208

merged 2 commits into from
Oct 25, 2024

Conversation

Nugine
Copy link
Owner

@Nugine Nugine commented Oct 25, 2024

No description provided.

@Nugine
Copy link
Owner Author

Nugine commented Oct 25, 2024

@mergify queue

Copy link

mergify bot commented Oct 25, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 8961184

Copy link

mergify bot commented Oct 25, 2024

This pull request, with head sha 896118407647b1c8c1a3c49df6d363e41caee27d, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha 896118407647b1c8c1a3c49df6d363e41caee27d is part of the main branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch feat/sig, this means GitHub will fail to detect the merge.

@mergify mergify bot merged commit 8961184 into main Oct 25, 2024
11 of 14 checks passed
@Nugine Nugine deleted the feat/sig branch October 25, 2024 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant