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

fix: make releases work again without v in tags #2586

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

skylenet
Copy link
Collaborator

@skylenet skylenet commented Nov 1, 2024

Description

The release please config was put into the manifest file. That should not be the case. The config file is a separate file. That's why the config wasn't read and we ended up having the v prefix in the most recent 1.4.1 release.

More infos https://github.com/googleapis/release-please/blob/main/docs/manifest-releaser.md#bootstrap-manually

REMINDER: Tag Reviewers, so they get notified to review

Is this change user facing?

NO

References (if applicable)

@skylenet skylenet added this pull request to the merge queue Nov 1, 2024
Merged via the queue into main with commit a87f945 Nov 1, 2024
61 checks passed
@skylenet skylenet deleted the skylenet/fixup-releases-v branch November 1, 2024 12:09
github-merge-queue bot pushed a commit that referenced this pull request Nov 19, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.4.2](v1.4.1...1.4.2)
(2024-11-10)


### Bug Fixes

* don't include component name in release please tags
([#2590](#2590))
([28582cc](28582cc))
* make releases work again without v in tags
([#2586](#2586))
([a87f945](a87f945))
* remove closeChannelWhenEmpty busy loop
([#2594](#2594))
([dbb2193](dbb2193))
* wrong config structure for release please
([#2588](#2588))
([e7263c3](e7263c3))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: kurtosisbot <[email protected]>
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