diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0b8b3316..7a7ff760 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -226,47 +226,48 @@ This should almost always be done using the [`xrpl-codec-gen`](https://github.co ## Release 1. Checkout `main` (or your beta branch) and `git pull`. -1. Create a new branch (`git checkout -b `) to capture updates that take place during this process. -1. Update `HISTORY.md` to reflect release changes. +2. Create a new branch (`git checkout -b `) to capture updates that take place during this process. +3. Update `HISTORY.md` to reflect release changes. - [ ] Update the version number and release date, and ensure it lists the changes since the previous release. -1. Run `npm run docgen` if the docs were modified in this release to update them (skip this step for a beta). -1. Run `npm run build` to triple check the build still works -1. Run `npx lerna version --no-git-tag-version` - This bumps the package versions. +4. Run `npm run docgen` if the docs were modified in this release to update them (skip this step for a beta). +5. Run `npm run clean` to delete previously generated artifacts. +6. Run `npm run build` to triple check the build still works +7. Run `npx lerna version --no-git-tag-version` - This bumps the package versions. - For each changed package, pick what the new version should be. Lerna will bump the versions, commit version bumps to `main`, and create a new git tag for each published package. - If you do NOT want to update the package number, choose "Custom Version" and set the version to be the same as the existing version. Lerna will not publish any changes in this case. - If publishing a beta, make sure that the versions are all of the form `a.b.c-beta.d`, where `a`, `b`, and `c` are identical to the last normal release except for one, which has been incremented by 1. -1. Run `npm i` to update the package-lock with the updated versions. -1. Create a new PR from this branch into `main` and merge it (you can directly merge into the beta branch for a beta). -1. Checkout `main` and `git pull` (you can skip this step for a beta since you already have the latest version of the beta branch). -1. Actually publish the packages with one of the following: +8. Run `npm i` to update the package-lock with the updated versions. +9. Create a new PR from this branch into `main` and merge it (you can directly merge into the beta branch for a beta). +10. Checkout `main` and `git pull` (you can skip this step for a beta since you already have the latest version of the beta branch). +11. Actually publish the packages with one of the following: - - Stable release: Run `npx lerna publish from-package --yes` - - Beta release: Run `npx lerna publish from-package --dist-tag beta --yes` - Notice this allows developers to install the package with `npm add xahau@beta` + - Stable release: Run `npx lerna publish from-package --yes` + - Beta release: Run `npx lerna publish from-package --dist-tag beta --yes` + Notice this allows developers to install the package with `npm add xahau@beta` -1. If requested, enter your [npmjs.com](https://npmjs.com) OTP (one-time password) to complete publication. +12. If requested, enter your [npmjs.com](https://npmjs.com) OTP (one-time password) to complete publication. - NOW YOU HAVE PUBLISHED! But you're not done; we have to notify people! + NOW YOU HAVE PUBLISHED! But you're not done; we have to notify people! -1. Run `git tag -m `, where `` is the new package and version (e.g. `xahau@2.1.1`), for each version released. -1. Run `git push --follow-tags`, to push the tags to Github. -1. On GitHub, click the "Releases" link on the right-hand side of the page. +13. Run `git tag -m `, where `` is the new package and version (e.g. `xahau@2.1.1`), for each version released. +14. Run `git push --follow-tags`, to push the tags to Github. +15. On GitHub, click the "Releases" link on the right-hand side of the page. -1. Repeat for each release: +16. Repeat for each release: - 1. Click "Draft a new release" - 1. Click "Choose a tag", and choose a tag that you just created. - 1. Edit the name of the release to match the tag (IE \@\) and edit the description as you see fit. + 1. Click "Draft a new release" + 2. Click "Choose a tag", and choose a tag that you just created. + 3. Edit the name of the release to match the tag (IE \@\) and edit the description as you see fit. -1. Send an email to [xahau-announce](https://groups.google.com/g/xahau-announce). -1. Lastly, send a similar message to the Xahau Discord in the [`javascript` channel](https://discord.com/channels/1085202760548499486/1085203623111295068). The message should include: +17. Send an email to [xahau-announce](https://groups.google.com/g/xahau-announce). +18. Lastly, send a similar message to the Xahau Discord in the [`javascript` channel](https://discord.com/channels/1085202760548499486/1085203623111295068). The message should include: 1. The version changes for xahau libraries - 1. A link to the more detailed changes - 1. Highlights of important changes + 2. A link to the more detailed changes + 3. Highlights of important changes ## Mailing Lists diff --git a/packages/secret-numbers/HISTORY.md b/packages/secret-numbers/HISTORY.md index 15311a3e..b1201d5d 100644 --- a/packages/secret-numbers/HISTORY.md +++ b/packages/secret-numbers/HISTORY.md @@ -4,6 +4,9 @@ Subscribe to [the **xrpl-announce** mailing list](https://groups.google.com/g/xr ## Unreleased +### BREAKING CHANGES: +* Renamed `build/xrplf-secret-numbers-latest.min.js` to `build/xrplf-secret-numbers-latest-min.js`. + ## 1.0.0 (2024-02-01) ### BREAKING CHANGES: diff --git a/packages/secret-numbers/package.json b/packages/secret-numbers/package.json index 676f6e1a..bbad7c48 100644 --- a/packages/secret-numbers/package.json +++ b/packages/secret-numbers/package.json @@ -8,7 +8,7 @@ "types": "dist/index.d.ts", "scripts": { "prepublish": "npm run clean && npm run lint && npm run test && npm run test:browser && npm run build", - "clean": "rm -rf ./dist ./coverage ./test/testCompiledForWeb tsconfig.build.tsbuildinfo", + "clean": "rm -rf ./build ./dist ./coverage ./test/testCompiledForWeb tsconfig.build.tsbuildinfo", "test": "jest --verbose", "test:browser": "npm run build && npm run build:browserTests && karma start ./karma.config.js", "build": "run-s build:lib build:web", diff --git a/packages/xahau/HISTORY.md b/packages/xahau/HISTORY.md index cfdb5960..10aca78d 100644 --- a/packages/xahau/HISTORY.md +++ b/packages/xahau/HISTORY.md @@ -3,6 +3,10 @@ Subscribe to [the **xrpl-announce** mailing list](https://groups.google.com/g/xrpl-announce) for release announcements. We recommend that xrpl.js (ripple-lib) users stay up-to-date with the latest stable release. ## Unreleased Changes +### Added +* Fixed minified `build/xahau-latest-min.js` to have all the latest xahau package changes. + +## 4.0.1 (2025-11-12) ### Added * Support for Cron Amendment diff --git a/packages/xahau/package.json b/packages/xahau/package.json index f5778a23..c127a782 100644 --- a/packages/xahau/package.json +++ b/packages/xahau/package.json @@ -56,7 +56,7 @@ "build:browserTests": "webpack --config ./test/webpack.config.js", "analyze": "webpack --analyze", "watch": "run-s build:lib --watch", - "clean": "rm -rf ./dist ./coverage ./test/testCompiledForWeb tsconfig.build.tsbuildinfo", + "clean": "rm -rf ./build ./dist ./coverage ./test/testCompiledForWeb tsconfig.build.tsbuildinfo", "docgen": "tsc --build tsconfig.docs.json && typedoc && echo js.xahau.org >> ../../docs/CNAME", "prepare": "copyfiles ../../README.md xahau/README.md", "prepublish": "run-s clean build", diff --git a/webpack.config.js b/webpack.config.js index 5f1cf500..36bf177b 100644 --- a/webpack.config.js +++ b/webpack.config.js @@ -48,7 +48,7 @@ module.exports = { const localConfig = merge(config, { mode: "production", output: { - filename: `${filename}-latest.min.js`, + filename: `${filename}-latest-min.js`, }, });