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

[release-2.10] Bump github.com/minio/minio-go/v7 from 7.0.62 to 7.0.63 #5903

Merged
merged 1 commit into from
Sep 1, 2023

Conversation

grafanabot
Copy link
Contributor

Backport 98d7c85 from #5888

Bumps [github.com/minio/minio-go/v7](https://github.com/minio/minio-go) from 7.0.62 to 7.0.63.
- [Release notes](https://github.com/minio/minio-go/releases)
- [Commits](minio/minio-go@v7.0.62...v7.0.63)

---
updated-dependencies:
- dependency-name: github.com/minio/minio-go/v7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(cherry picked from commit 98d7c85)
@56quarters 56quarters enabled auto-merge (squash) September 1, 2023 14:54
@56quarters 56quarters merged commit 56759b9 into release-2.10 Sep 1, 2023
@56quarters 56quarters deleted the backport-5888-to-release-2.10 branch September 1, 2023 14:57
@pstibrany
Copy link
Member

Can we add changelog to mention this in rc.1? What exactly does it fix?

@56quarters
Copy link
Contributor

Can we add changelog to mention this in rc.1? What exactly does it fix?

I guess? We didn't add a changelog entry for the initial PR. Does the presence of an issue (#5878) necessitate a changelog entry for routine version bumps?

@pstibrany
Copy link
Member

Can we add changelog to mention this in rc.1? What exactly does it fix?

I guess? We didn't add a changelog entry for the initial PR. Does the presence of an issue (#5878) necessitate a changelog entry for routine version bumps?

We don't do "routine version bumps" between release candidates, but we did it here. There must be a reason, and it would be good to document it.

@56quarters
Copy link
Contributor

Can we add changelog to mention this in rc.1? What exactly does it fix?

I guess? We didn't add a changelog entry for the initial PR. Does the presence of an issue (#5878) necessitate a changelog entry for routine version bumps?

We don't do "routine version bumps" between release candidates, but we did it here. There must be a reason, and it would be good to document it.

Alright, I'll add a changelog.

@colega
Copy link
Contributor

colega commented Sep 1, 2023

I'll hold publishing rc.1 until Monday to include that changelog 👍

56quarters added a commit that referenced this pull request Sep 1, 2023
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
@56quarters
Copy link
Contributor

Opened #5905

56quarters added a commit that referenced this pull request Sep 1, 2023
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants