@keeper-security/keeper-js-ui 0.23.1 → 0.25.0

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [0.25.0](https://github.com/Keeper-Security/keeper-js-ui/compare/v0.24.0...v0.25.0) (2026-05-12)
+
+
+### Features
+
+* **Icon:** add BreachwatchIcon ([#553](https://github.com/Keeper-Security/keeper-js-ui/issues/553)) ([c22363c](https://github.com/Keeper-Security/keeper-js-ui/commit/c22363cc60229db5aa079e23b5764006a62a652e))
+
+
+### Bug Fixes
+
+* **Checkbox:** adjust dimensions and add new icon ([#554](https://github.com/Keeper-Security/keeper-js-ui/issues/554)) ([5703eeb](https://github.com/Keeper-Security/keeper-js-ui/commit/5703eeb9315c70d4e2cb726bf151102bca758fb9))
+
+## [0.24.0](https://github.com/Keeper-Security/keeper-js-ui/compare/v0.23.1...v0.24.0) (2026-05-05)
+
+
+### Features
+
+* **Indicator:** add component to library ([#536](https://github.com/Keeper-Security/keeper-js-ui/issues/536)) ([f36e3a6](https://github.com/Keeper-Security/keeper-js-ui/commit/f36e3a6b5584f1c42d712146642a36d7f970d203))
+
+
+### Bug Fixes
+
+* **ListItemText:** adjust font-size in compact density ([#547](https://github.com/Keeper-Security/keeper-js-ui/issues/547)) ([d895bd1](https://github.com/Keeper-Security/keeper-js-ui/commit/d895bd1bc7a1d72a4882f720479bc9a95e421872))
+
 ## [0.23.1](https://github.com/Keeper-Security/keeper-js-ui/compare/v0.23.0...v0.23.1) (2026-05-05)
 
 

package/README.md

@@ -149,6 +149,22 @@ Your best bet is to use one of [Windows' High Contrast Themes](https://learn.mic
   4. Select `Emulate CSS forced-colors: active`.
   5. To deactivate, repeat the `Run` command but select `Do not emulate CSS forced-colors`.
 
+## Deprecating Components, Props, and Values
+
+While we strive for stable APIs, mistakes happen. The goal of a deprecation
+is to inform consumers that something has changed, provide an alternative,
+and allow enough time for migration before removal.
+
+### Deprecating an Entire Component
+
+### Deprecating a Prop
+
+### Deprecating a Value
+
+### Runtime Warnings (Optional)
+
+### Commit, Changelog, and PR
+
 ## Adding Icons
 
 1. Create a `.tsx` file in `src/icons`.
@@ -507,30 +523,31 @@ A `dist` folder will be created at the root of the project. This folder is ignor
 
 Before publishing, you want to make sure that external projects have access to expected components and intellisense/autocomplete still works.
 
-[npm link](https://docs.npmjs.com/cli/v9/commands/npm-link) can be flakey, so the alternative would be run [npm pack](https://docs.npmjs.com/cli/v9/commands/npm-pack) to create a local \*.tgz file and install that file in your external project.
+[npm link](https://docs.npmjs.com/cli/v9/commands/npm-link) can be flakey, so the alternative would be run [npm pack](https://docs.npmjs.com/cli/v9/commands/npm-pack) to create a local \*.tgz file in the library and install that file into the external project importing the library.
 
-0. (Optional): Update your `package.json` version number, **_but don't commit it_**. This step is automated with the correct next version number.
-1. Run:
+0. (Optional): Update the library's `package.json` version number, **_but don't commit it_**. This step is automated with the correct next version number.
+1. From the library, run:
 
 ```sh
 npm run build && npm pack
 ```
 
-2. Copy the name and location of the new `*.tgz` file that was created.
-3. Update your external project's `package.json` reference to the library.
+2. Copy the name and location of the new `*.tgz` file that was created at the root of the library.
+3. Switch over to the project that is importing the library (e.g. Browser Extension).
+4. Update that project's `package.json` reference to the library.
 
 ```diff
 - "@keeper-security/keeper-js-ui": "1.0.0",
 + "@keeper-security/keeper-js-ui": "file://../keeper-js-ui/keeper-security-keeper-js-ui-1.0.0.tgz",
 ```
 
-4. Run:
+5. From the external project, run:
 
 ```sh
 npm install
 ```
 
-5. After testing for component behavior and availability, as well as intellisense/autocomplete and TypeScript prop validation, undo your package reference changes to `package.json` & `package-lock.json`. **_Do not commit them into your external project._**
+6. After testing for component behavior and availability, as well as intellisense/autocomplete and TypeScript prop validation, undo your package reference changes to `package.json` & `package-lock.json`. **_Do not commit them into your external project._**
 
 ## Publishing an NPM Package