@commercetools-frontend-extensions/change-history 8.22.0 → 8.24.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -7
- package/dist/commercetools-frontend-extensions-change-history.cjs.dev.js +3672 -2866
- package/dist/commercetools-frontend-extensions-change-history.cjs.prod.js +3711 -3027
- package/dist/commercetools-frontend-extensions-change-history.esm.js +3685 -2880
- package/dist/{de-d88ec50e.esm.js → de-7764939f.esm.js} +12 -16
- package/dist/{de-18cad55a.cjs.dev.js → de-ad037854.cjs.dev.js} +12 -16
- package/dist/{de-880c7172.cjs.prod.js → de-c2be9253.cjs.prod.js} +12 -16
- package/dist/{en-70c04202.esm.js → en-1c982e4c.esm.js} +12 -16
- package/dist/{en-623b9ecb.cjs.prod.js → en-87dd4629.cjs.dev.js} +12 -16
- package/dist/{en-1a9e77cd.cjs.dev.js → en-f0b11682.cjs.prod.js} +12 -16
- package/dist/{es-929d0897.cjs.dev.js → es-0421b67e.cjs.prod.js} +12 -16
- package/dist/{es-d8f2c3ee.esm.js → es-83f1bc1c.esm.js} +12 -16
- package/dist/{es-6eaa2235.cjs.prod.js → es-dee2e5ce.cjs.dev.js} +12 -16
- package/dist/{fr-FR-9edf8a40.esm.js → fr-FR-49d3b2ef.esm.js} +12 -16
- package/dist/{fr-FR-a1b30f0a.cjs.dev.js → fr-FR-a3c8a9b8.cjs.prod.js} +12 -16
- package/dist/{fr-FR-d1a8524a.cjs.prod.js → fr-FR-f37fb0ff.cjs.dev.js} +12 -16
- package/dist/{pt-BR-f543fdc3.cjs.prod.js → pt-BR-4e486b02.cjs.prod.js} +12 -16
- package/dist/{pt-BR-b54f0fdb.cjs.dev.js → pt-BR-8a1c2b7a.cjs.dev.js} +12 -16
- package/dist/{pt-BR-d7458b1e.esm.js → pt-BR-eb64f196.esm.js} +12 -16
- package/dist/{zh-CN-210ea4af.cjs.prod.js → zh-CN-252dd3b1.cjs.prod.js} +12 -16
- package/dist/{zh-CN-a6c09d9a.esm.js → zh-CN-9ac999ed.esm.js} +12 -16
- package/dist/{zh-CN-117c7d99.cjs.dev.js → zh-CN-f319b1ad.cjs.dev.js} +12 -16
- package/package.json +25 -25
package/README.md
CHANGED
|
@@ -6,7 +6,6 @@ Package for building and integrating Commercetools Change History feature into y
|
|
|
6
6
|
|
|
7
7
|
> The components follow the same principles of the [UIKit](https://github.com/commercetools/ui-kit) components, but are more specific to Change History.
|
|
8
8
|
|
|
9
|
-
|
|
10
9
|
## Getting started
|
|
11
10
|
|
|
12
11
|
```bash
|
|
@@ -28,17 +27,16 @@ In case you want to publish a new version with the latest changes you need to:
|
|
|
28
27
|
|
|
29
28
|
1. Add a changeset with `pnpm exec changeset` and select `@commercetools-frontend-extensions/change-history` as the modified package.
|
|
30
29
|
2. Some options would be appear in order to do the release:
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
30
|
+
- `patch`: use this release for fixes or small changes
|
|
31
|
+
- `minor`: use this release for depenency upgrades or medium changes
|
|
32
|
+
- `major`: use this release for breaking changes
|
|
34
33
|
3. After selecting the option you will need to add a comment for the release notes. We recommend to use the same format as for the commits.
|
|
35
|
-
|
|
34
|
+
- e.g: `feat(utils): add utils for dates`
|
|
36
35
|
4. Push the `changeset` to your branch and GitHub actions will detect that the PR contains changes that affect the published library.
|
|
37
36
|
5. After the PR gets merged, another PR will be created called `Version Packages` which is the one that will be detected, again by GitHub Actions, to do a release to NPM.
|
|
38
37
|
6. Make sure that everything is correct and then merge `Version Packages` PR.
|
|
39
38
|
7. Wait until the new version is available in NPM and then deploy the custom in CircleCI.
|
|
40
39
|
|
|
41
|
-
|
|
42
40
|
## i18n
|
|
43
41
|
|
|
44
42
|
The repo is configured with an integration with Transifex. The process for i18n is the same as the Merchant Center uses.
|
|
@@ -57,4 +55,9 @@ On `main` branch, we automatically publish **canary** releases from CI to the `c
|
|
|
57
55
|
|
|
58
56
|
Canary releases are useful to test early changes that should not be released yet to `next` or `latest`. They are automatically triggered and released after a Pull Request merged into `main`, unless the commit message contains `[skip publish]`.
|
|
59
57
|
|
|
60
|
-
|
|
58
|
+
In order to generate a canary release, the code must be merged into `main` with a changeset. To access the tag, you can either:
|
|
59
|
+
|
|
60
|
+
- Navigate to https://www.npmjs.com/package/@commercetools-frontend-extensions/change-history?activeTab=versions for the current and past versions.
|
|
61
|
+
- Run `pnpm info @commercetools-frontend-extensions/change-history` in the terminal.
|
|
62
|
+
|
|
63
|
+
Note that canary releases **will not create git tags and version bump commits**.
|