Skip to content

chore(dev): release 6.7.0#1960

Closed
release-please[bot] wants to merge 1 commit into
devfrom
release-please--branches--dev--components--com.microsoft.graph.microsoft-graph
Closed

chore(dev): release 6.7.0#1960
release-please[bot] wants to merge 1 commit into
devfrom
release-please--branches--dev--components--com.microsoft.graph.microsoft-graph

Conversation

@release-please

@release-please release-please Bot commented Apr 24, 2024

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

6.7.0 (2024-04-25)

Features

  • generation: update request builders and models (747366c)

This PR was generated with Release Please. See documentation.

@calebkiage

This comment was marked as outdated.

@release-please release-please Bot force-pushed the release-please--branches--dev--components--com.microsoft.graph.microsoft-graph branch from fc7e8a7 to 2afc0a8 Compare April 25, 2024 06:40
@calebkiage

This comment was marked as resolved.

@baywet

baywet commented Apr 25, 2024

Copy link
Copy Markdown
Member

@calebkiage since the 6.7.0 release already went out, shouldn't this one have been closed automatically? (learning here)

@calebkiage

calebkiage commented Apr 25, 2024

Copy link
Copy Markdown
Contributor

@baywet, I don't think the bot will close the PR automatically. The version config is what determines the 1st release. Once pr #1964 is merged, then this PR should be closed (or updated) automatically.

@calebkiage calebkiage closed this Apr 25, 2024
@calebkiage calebkiage deleted the release-please--branches--dev--components--com.microsoft.graph.microsoft-graph branch April 25, 2024 19:11
@calebkiage

Copy link
Copy Markdown
Contributor

Upon reading the docs, the bot won't create a PR if there's another one open. I've closed this PR so the bot can create a PR successfully.

A new PR will be opened when commits of either of the types feat or fix are merged into dev.

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