chore(main): release server-sdk 1.22.0

[openfeaturebot]

🤖 I have created a release beep boop

1.22.0 (2026-06-12)

✨ New Features

• expose js sdk identity on client metadata (#1376) (6c437e7)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Code Review

This pull request updates @openfeature/server-sdk to version 1.22.0 and introduces a new feature to expose JS SDK identity on client metadata. The review feedback points out a discrepancy between the devDependencies and peerDependencies versions for @openfeature/core, suggesting that peerDependencies should be updated to maintain compatibility for the new feature. Additionally, it is suggested to remove development dependency updates from the changelog as they typically do not affect end-users.

[gemini-code-assist]

Including devDependencies updates in the changelog is unusual as these changes typically do not affect the end-users of the package. If this bump to @openfeature/core v1.11.0 is required for the new "js sdk identity" feature to function correctly (e.g., due to type changes or new metadata fields), then the peerDependencies in package.json should likely be updated as well. If it is purely a development-time dependency update, it should probably be removed from the changelog to avoid confusion.

[gemini-code-assist]

The devDependencies for @openfeature/core has been bumped to ^1.11.0, but the peerDependencies (on line 51) remains at ^1.10.0. If the new feature "expose js sdk identity on client metadata" relies on functionality or types introduced in @openfeature/core v1.11.0, the peerDependencies should also be updated to ^1.11.0. This ensures that consumers of the SDK are using a compatible version of the core package and prevents potential runtime or type errors.