[configcat] Release request

[adams85]

Hi!

I'm not sure if this is the right place to ask but we'd like to request a release of the ConfigCat providers because of this update: #1371

Since this is a breaking change, both providers (config-cat-provider and config-cat-web-provider) and the shared package (config-cat-core) should be released with a new major version.

Can you explain how to proceed with this?

[beeme1mr]

Hey @adams85, it doesn't look like core is marked as a breaking change right now. Is the breaking change the bump to the configcat dependency?

I can try and help release the updates. FYI @lukas-reining

[lukas-reining]

@beeme1mr it seems like no release-please PRs have been opened after merging #1371
These are the latest PRs: https://github.com/open-feature/js-sdk-contrib/pulls?q=is%3Apr+config-cat

[adams85]

Hi @beeme1mr,

Thanks for your help.

Is the breaking change the bump to the configcat dependency?

Yes, it is - among other things like slight changes to the evaluation context transformation. We should increase the major version of core as well.

[beeme1mr]

Okay, I understand now. How about I do the following:

1. Release version 0.2.0 of ConfigCat core. This is considered a breaking change since we're sub-v1 and the release notes will explicitly mention the change.
2. We can then bump the config-cat-core dependency to 0.2.0 here and here.
3. We release @openfeature/config-cat-provider as version 0.8.0 and @openfeature/config-cat-web-provider as 0.2.0

Does that plan sound reasonable? If so, I can knock it out tomorrow.

[adams85]

Hmm, I hadn't realize until now that these packages are sub-v1...

In that case, increasing the minor versions sounds reasonable, especially if the release notes include some hints on the BCs.

[toddbaert]

I released https://www.npmjs.com/package/@openfeature/config-cat-provider/v/0.8.0?activeTab=versions and https://www.npmjs.com/package/@openfeature/config-cat-web-provider/v/0.2.0

[adams85]

Thank you, @toddbaert!

According to my tests everything works fine, I only found a minor hitch: the provider packages reference @configcat/sdk as a peer dependency, while the core package references it as a normal dependency, which kind of defeats the purpose of the peer dependency - if my understanding of NPM dependency handling is correct.

However, this doesn't look like something that would require a new release ASAP. We can fix this the next time we make some changes.