Conversation
…ns to CONTRIBUTING.md
| @@ -0,0 +1,20 @@ | |||
| # openfeature-js-client | |||
|
|
|||
| Monorepo using **Lerna** with **fixed versioning** — all packages share the version in `lerna.json`. | |||
There was a problem hiding this comment.
This looks like it locks us into having the same version for browser and node packages, and always releasing the two simultaneously. This doesn't seem desirable given how little overlap there is.
Although this looks like it isn't new, now might be a good time to revisit this.
There was a problem hiding this comment.
Yea thanks for bringing it up; right it's the existing procedure but I agree it feels undesirable given they are totally different targets.
If we continue like this, almost all server releases will be empty. It is up to dd-trace-js to pick them up as needed. Do you think this makes upgrade dd-trace-js harder?
There was a problem hiding this comment.
I guess my main worry is having more major version bumps than necessary. For all the reason, including users not getting automated updates and having to bump dependency version on their end
…r description - Move IndexedDB persistence and RUM tracking items to Public Changes section - Fix node-server package.json description from "React Native" to "Node.js server"
Co-authored-by: Oleksii Shmalko <[email protected]>
2 participants
Motivation
Prepare minor release v1.1.0 with changes accumulated since v1.0.0 GA.
Changes
@datadog/flagging-core,@datadog/openfeature-browser,@datadog/openfeature-node-server) from 1.0.0 to 1.1.0Notable changes in this release:
Decisions
latestnpm tag (production release, not prerelease)v1.1.0(non-prerelease) to trigger automated publishing