@commercetools-frontend-extensions/change-history 8.11.0 → 8.13.0

package/LICENSE

@@ -1,29 +1,21 @@
-BSD 3-Clause License
+MIT License
 
-Copyright (c) 2020, commercetools GmbH
-All rights reserved.
+Copyright (c) commercetools GmbH
 
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-1. Redistributions of source code must retain the above copyright notice, this
-   list of conditions and the following disclaimer.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
-2. Redistributions in binary form must reproduce the above copyright notice,
-   this list of conditions and the following disclaimer in the documentation
-   and/or other materials provided with the distribution.
-
-3. Neither the name of the copyright holder nor the names of its
-   contributors may be used to endorse or promote products derived from
-   this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -10,11 +10,14 @@ Package for building and integrating Commercetools Change History feature into y
 ## Getting started
 
 ```bash
+# npm
 $ npm install --save @commercetools-frontend-extensions/change-history
 
-// or
-
+# yarn
 $ yarn add @commercetools-frontend-extensions/change-history
+
+# pnpm
+$ pnpm add @commercetools-frontend-extensions/change-history
 ```
 
 ## Releasing
@@ -23,7 +26,7 @@ This package uses [`changesets`](https://github.com/atlassian/changesets) in ord
 
 In case you want to publish a new version with the latest changes you need to:
 
-1. Add a changeset with `yarn changeset` and select `@commercetools-frontend-extensions/change-history` as the modified package.
+1. Add a changeset with `pnpm exec changeset` and select `@commercetools-frontend-extensions/change-history` as the modified package.
 2. Some options would be appear in order to do the release:
     * `patch`: use this release for fixes or small changes 
     * `minor`: use this release for depenency upgrades or medium changes
@@ -40,9 +43,9 @@ In case you want to publish a new version with the latest changes you need to:
 
 The repo is configured with an integration with Transifex. The process for i18n is the same as the Merchant Center uses.
 
-`yarn i18n:build` for adding the new keys to transifex.
+`pnpm run i18n:build` for adding the new keys to transifex.
 
-Once the PR gets merged to `master` transifex will receive a notification with new keys that need to be translated (that's why is important that `description` and `defaultMessage` are descriptive enough).
+Once the PR gets merged to `main` transifex will receive a notification with new keys that need to be translated (that's why is important that `description` and `defaultMessage` are descriptive enough).
 
 Whenever the translators finish translations and mark them as done, the repo will receive a PR (per language) for adding translated messages.