chore(main): release OpenFeature.Contrib.Hooks.Otel 0.1.4

[github-actions]

🤖 I have created a release beep boop

0.1.4 (2024-01-25)

🧹 Chore

• Add support for GitHub Packages (#134) (0def0da)

---

This PR was generated with Release Please. See documentation.

[austindrenski]

Approving but want to call out that there are several relevant commits not being picked up by the release-please bot, most notably the reduction in dependencies used by this package, as well as the shared SDK version bump...

Not sure if that's something we can configure/fix, but might be worth some thought before we get to the next major/breaking release.

[toddbaert]

Approving but want to call out that there are several relevant commits not being picked up by the release-please bot, most notably the reduction in dependencies used by this package, as well as the shared SDK version bump...

Not sure if that's something we can configure/fix, but might be worth some thought before we get to the next major/breaking release.

Release please only picks up on changes within the component subfolder (like I mentioned here). I'm not sure exactly what changes you're referring to, but I'm guessing they we in the parent dir(s)?

[toddbaert]

Oh, is it #132?

Ya, actually, that's very strange. I wonder if it's the "refactor" semantic commit type? I would think that should work fine, but I maybe it's not supported 🤔

Nope, that's captured in a recent release from Jan 11: https://github.com/open-feature/dotnet-sdk-contrib/releases/tag/OpenFeature.Contrib.Hooks.Otel-v0.1.3 (release please PR here)

@austindrenski does this release contain what you were worried about? Is there anything else missing?

[austindrenski]

Oh, is it #132?

Ya, actually, that's very strange. I wonder if it's the "refactor" semantic commit type? I would think that should work fine, but I maybe it's not supported 🤔

Nope, that's captured in a recent release from Jan 11: https://github.com/open-feature/dotnet-sdk-contrib/releases/tag/OpenFeature.Contrib.Hooks.Otel-v0.1.3 (release please PR here)

@austindrenski does this release contain what you were worried about? Is there anything else missing?

Oh woof, you're right, sorry, for some reason I had it in my head that #132 landed late last week, so wasn't expecting it to have been released already 🤦

Release please only picks up on changes within the component subfolder (like I mentioned here). I'm not sure exactly what changes you're referring to, but I'm guessing they we in the parent dir(s)?

The other one I was referencing was #144 which, as you surmised, did not touch anything in this directory, but it did touch the shared SDK which makes me think that perhaps we need to configure release-please to understand the *.csproj -> ../Directory.Build.props -> ../build/Common.prod.props -> ../build/Common.props linkages?

Idk, not a big deal for now, just thinking that it would be nice to have repo-wide effects captured in these changelogs as we attract more consumers and contributors over time.

[austindrenski]

@open-feature/sdk-dotnet-maintainers Can I get a second approval on this so we can get a stable version of this package released with support for #144?

[github-actions]

🤖 Release is at https://github.com/open-feature/dotnet-sdk-contrib/releases/tag/OpenFeature.Contrib.Hooks.Otel-v0.1.4 🌻