Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 15, 2025

Bumps github.com/aws/aws-sdk-go-v2/service/s3 from 1.93.0 to 1.93.2.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/aws/aws-sdk-go-v2/service/s3](https://github.com/aws/aws-sdk-go-v2) from 1.93.0 to 1.93.2.
- [Release notes](https://github.com/aws/aws-sdk-go-v2/releases)
- [Changelog](https://github.com/aws/aws-sdk-go-v2/blob/main/changelog-template.json)
- [Commits](aws/aws-sdk-go-v2@service/s3/v1.93.0...service/s3/v1.93.2)

---
updated-dependencies:
- dependency-name: github.com/aws/aws-sdk-go-v2/service/s3
  dependency-version: 1.93.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Dec 15, 2025
@dependabot dependabot bot requested a review from a team as a code owner December 15, 2025 07:03
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Dec 15, 2025
@github-actions
Copy link

⚠️ E2E Tests Skipped

The E2E tests were skipped because the E2E_TOKEN secret is not configured in this repository. The skip-e2e label has been added to prevent future E2E test runs on this PR.

To enable E2E tests, please:

  1. Go to your repository Settings → Secrets and variables → Actions
  2. Add a new repository secret named E2E_TOKEN
  3. Set the value to a valid Azion personal token
  4. Remove the skip-e2e label from this PR

Once configured, the E2E tests will run automatically on future pull requests.

@github-actions github-actions bot added the skip-e2e Skip e2e tests, for scenarios where the API is still not deployed label Dec 15, 2025
@github-actions
Copy link

⚠️ E2E Tests Skipped

The E2E tests were skipped because the E2E_TOKEN secret is not configured in this repository. The skip-e2e label has been added to prevent future E2E test runs on this PR.

To enable E2E tests, please:

  1. Go to your repository Settings → Secrets and variables → Actions
  2. Add a new repository secret named E2E_TOKEN
  3. Set the value to a valid Azion personal token
  4. Remove the skip-e2e label from this PR

Once configured, the E2E tests will run automatically on future pull requests.

3 similar comments
@github-actions
Copy link

⚠️ E2E Tests Skipped

The E2E tests were skipped because the E2E_TOKEN secret is not configured in this repository. The skip-e2e label has been added to prevent future E2E test runs on this PR.

To enable E2E tests, please:

  1. Go to your repository Settings → Secrets and variables → Actions
  2. Add a new repository secret named E2E_TOKEN
  3. Set the value to a valid Azion personal token
  4. Remove the skip-e2e label from this PR

Once configured, the E2E tests will run automatically on future pull requests.

@github-actions
Copy link

⚠️ E2E Tests Skipped

The E2E tests were skipped because the E2E_TOKEN secret is not configured in this repository. The skip-e2e label has been added to prevent future E2E test runs on this PR.

To enable E2E tests, please:

  1. Go to your repository Settings → Secrets and variables → Actions
  2. Add a new repository secret named E2E_TOKEN
  3. Set the value to a valid Azion personal token
  4. Remove the skip-e2e label from this PR

Once configured, the E2E tests will run automatically on future pull requests.

@github-actions
Copy link

⚠️ E2E Tests Skipped

The E2E tests were skipped because the E2E_TOKEN secret is not configured in this repository. The skip-e2e label has been added to prevent future E2E test runs on this PR.

To enable E2E tests, please:

  1. Go to your repository Settings → Secrets and variables → Actions
  2. Add a new repository secret named E2E_TOKEN
  3. Set the value to a valid Azion personal token
  4. Remove the skip-e2e label from this PR

Once configured, the E2E tests will run automatically on future pull requests.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 22, 2025

Superseded by #1363.

@dependabot dependabot bot closed this Dec 22, 2025
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.93.2 branch December 22, 2025 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code skip-e2e Skip e2e tests, for scenarios where the API is still not deployed

Development

Successfully merging this pull request may close these issues.

1 participant