GRIN/nym

Files

T

Jędrzej Stuczyński 5a0db2aea4 always using port 443 for tls gateway connection (#3927 )

* always using port 443 for tls gateway connection

* bumping up rc version

* hack: additional hardcoded gateways

it disables topology refresh

* Add NPM packages to tool for bumping versions

* Bump RC versions of SDK packages

* Use manual gateway details

* Add progress to `publish.sh` script

* Add docs for WSS workaround

---------

Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>

2023-09-22 15:35:14 +01:00

src

always using port 443 for tls gateway connection (#3927 )

2023-09-22 15:35:14 +01:00

Cargo.toml

feat: mixFetch - the final countdown (#3737 )

2023-09-07 12:45:03 +01:00

README.md

feat: mixFetch - the final countdown (#3737 )

2023-09-07 12:45:03 +01:00

README.md

sdk-version-bump

simple tool to update version numbers of our sdk packages.

Usage:

note: this tool is expected to be run during CI, but if one wants to do it manually:

For releases:

run ./sdk-version-bump remove-suffix that will remove the -rc.X suffixes from all relevant packages
build everything and publish it to npm
run ./sdk-version-bump bump-version that will update the versions of all relevant packages from X.Y.Z into X.Y.(Z+1)-rc.0. It will also update the @nymproject/... dependencies from ">=X.Y.Z-rc.0 || ^X" to ">=X.Y.(Z+1)-rc.0 || ^X"

For pre-releases:

run ./sdk-version-bump bump-version --pre-release that will update the release candidate version of all relevant packages from X.Y.Z-rc.W to X.Y.Z-rc.(W+1)

To run it from the root, do: cargo run -p sdk-version-bump