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

chore(main): release 1.2.0 #308

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Jul 10, 2024

🤖 I have created a release beep boop

1.2.0 (2024-07-15)

Features

Bug Fixes

  • allows registration of page iterator headers (#309) (d4b0806)
  • content range order during upload (#304) (f241e94)

This PR was generated with Release Please. See documentation.

@release-please release-please bot requested a review from a team as a code owner July 10, 2024 12:19
Copy link
Member

@baywet baywet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@calebkiage something seems wrong with a configuration. When the earlier release pull request was merged it triggered a new release for release please. Do you have any idea of what could be wrong? I believe it could be the hash that has not been generated properly at the beginning.

@calebkiage
Copy link

This might be a bug related to googleapis/release-please#2329

@release-please release-please bot force-pushed the release-please--branches--main--components--github.com/microsoftgraph/msgraph-sdk-go-core branch from 509d099 to 34df9ff Compare July 15, 2024 06:36
Copy link

sonarcloud bot commented Jul 15, 2024

@baywet baywet merged commit e078aab into main Jul 15, 2024
8 checks passed
@baywet baywet deleted the release-please--branches--main--components--github.com/microsoftgraph/msgraph-sdk-go-core branch July 15, 2024 11:36
Copy link
Contributor Author

🤖 Created releases:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants