Skip to content

chore: exclude component in git tag#190

Merged
AlexsJones merged 1 commit into
mainfrom
beeme1mr-patch-1
Oct 13, 2022
Merged

chore: exclude component in git tag#190
AlexsJones merged 1 commit into
mainfrom
beeme1mr-patch-1

Conversation

@beeme1mr
Copy link
Copy Markdown
Member

This change prevents Release Please from adding the component name in the release tag. It looks like currently that's not a problem but this will prevent it from happening if the component name detection changes in the future.

Signed-off-by: Michael Beemer beeme1mr@users.noreply.github.com

This change prevents Release Please from adding the component name in the release tag. It looks like currently that's not a problem but this will prevent it from happening if the component name detection changes in the future.

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@AlexsJones
Copy link
Copy Markdown
Member

Just for posterity can you give an example?

@toddbaert
Copy link
Copy Markdown
Member

Just for posterity can you give an example?

Here's a release that has a component name in Java: https://github.com/open-feature/java-sdk/releases/tag/dev.openfeature.javasdk-v0.2.2

Instead of the tag just being 0.2.2 like would be preferred in a repo with only a single artifact, there's a "component name" in the tag (dev.openfeature.javasdk).

@AlexsJones AlexsJones merged commit 84e32b7 into main Oct 13, 2022
@AlexsJones AlexsJones deleted the beeme1mr-patch-1 branch October 13, 2022 08:41
raphael-wigoutschnigg-dt pushed a commit to open-feature-forking/flagd that referenced this pull request Mar 11, 2025
… v1.10.1 (open-feature#190)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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.

3 participants