@commercetools-frontend-extensions/change-history 8.34.0 → 8.35.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 +13 -13
- package/dist/commercetools-frontend-extensions-change-history.cjs.dev.js +3024 -2281
- package/dist/commercetools-frontend-extensions-change-history.cjs.prod.js +2967 -1361
- package/dist/commercetools-frontend-extensions-change-history.esm.js +3016 -2270
- package/dist/declarations/src/constants/filters.d.ts +22 -24
- package/dist/declarations/src/constants/index.d.ts +1 -0
- package/dist/declarations/src/constants/old-filters.d.ts +44 -0
- package/dist/declarations/src/i18n/use-async-intl-messages.d.ts +2 -2
- package/package.json +44 -54
package/README.md
CHANGED
|
@@ -35,19 +35,7 @@ In case you want to publish a new version with the latest changes you need to:
|
|
|
35
35
|
4. Push the `changeset` to your branch and GitHub actions will detect that the PR contains changes that affect the published library.
|
|
36
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.
|
|
37
37
|
6. Make sure that everything is correct and then merge `Version Packages` PR.
|
|
38
|
-
7.
|
|
39
|
-
|
|
40
|
-
## i18n
|
|
41
|
-
|
|
42
|
-
The repo is configured with an integration with Transifex. The process for i18n is the same as the Merchant Center uses.
|
|
43
|
-
|
|
44
|
-
`pnpm run i18n:build` for adding the new keys to transifex.
|
|
45
|
-
|
|
46
|
-
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).
|
|
47
|
-
|
|
48
|
-
Whenever the translators finish translations and mark them as done, the repo will receive a PR (per language) for adding translated messages.
|
|
49
|
-
|
|
50
|
-
Once we review that translated keys are correct and add a `changeset` we can merge the PR. (Don't forget to deploy the custom app)
|
|
38
|
+
7. Once the new version is published by NPM, the package will be available to be consumed manually and/or on schedule by Renovate.
|
|
51
39
|
|
|
52
40
|
## Canary releases
|
|
53
41
|
|
|
@@ -61,3 +49,15 @@ In order to generate a canary release, the code must be merged into `main` with
|
|
|
61
49
|
- Run `pnpm info @commercetools-frontend-extensions/change-history` in the terminal.
|
|
62
50
|
|
|
63
51
|
Note that canary releases **will not create git tags and version bump commits**.
|
|
52
|
+
|
|
53
|
+
## i18n
|
|
54
|
+
|
|
55
|
+
The repo is configured with an integration with Transifex. The process for i18n is the same as the Merchant Center uses.
|
|
56
|
+
|
|
57
|
+
`pnpm run i18n:build` for adding the new keys to transifex.
|
|
58
|
+
|
|
59
|
+
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).
|
|
60
|
+
|
|
61
|
+
Whenever the translators finish translations and mark them as done, the repo will receive a PR (per language) for adding translated messages.
|
|
62
|
+
|
|
63
|
+
Once we review that translated keys are correct and add a `changeset` we can merge the PR. (Don't forget to deploy the custom app)
|