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

ci: help release-please use the right latest release #481

Merged
merged 1 commit into from
Aug 25, 2023
Merged

Conversation

apricote
Copy link
Member

Release-please created a PR for 1.7.0 instead of the correct 2.4.0 because the releases in between were done outside of the main branch.

I am not sure that this actually fixes the issue, but we will see once release-please runs.

Release-please created a PR for 1.7.0 instead of the correct 2.4.0
because the releases in between were done outside of the main branch.

I am not sure that this actually fixes the issue, but we will see once
release-please runs.
@apricote apricote self-assigned this Aug 25, 2023
@apricote apricote requested a review from a team as a code owner August 25, 2023 10:13
@apricote apricote merged commit 66931d8 into main Aug 25, 2023
6 checks passed
@apricote apricote deleted the release-please branch August 25, 2023 10:17
lukasmetzner pushed a commit that referenced this pull request Oct 10, 2024
Release-please created a PR for 1.7.0 instead of the correct 2.4.0
because the releases in between were done outside of the main branch.

I am not sure that this actually fixes the issue, but we will see once
release-please runs.
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.

2 participants