@trezor/connect-common - npm Package Compare versions

Comparing version 0.0.6 to 0.0.7

CHANGELOG.md

package.json

		{
		"name": "@trezor/connect-common",
		"version": "0.0.6",
		"version": "0.0.7",
		"author": "Trezor <info@trezor.io>",
		"homepage": "https://github.com/trezor/trezor-suite/packages/connect-common",
		"homepage": "https://github.com/trezor/trezor-suite/tree/develop/packages/connect-common",
		"keywords": [
		@@ -7,0 +7,0 @@ "Trezor",

README.md

		@@ -8,4 +8,22 @@ # @trezor/connect-common

		### Publishing
		## files

		### bridge

		Data in `releases.json` are used to determin which version of Bridge to use depending on the user's operating system.

		### firmware

		Binaries of the latest versions of firmware for each Trezor model are included in this package so that they are available to users of Suite desktop app without connecting to the internet. The process of adding new firmwares is described [here](../../docs/releases/adding-new-firmwares.md). Besides the latest versions, model One and model T both require a transitory version for upgrading from old firware (intermediary firmware `trezor-inter-1.10.0.bin` for model One and version `trezor-2.1.1.bin` for model T).

		There is a `releases.json` file for each Trezor model which must be updated any time new binaries are added. This file provides data about all available firmware versions and it is used to display them in Suite and to make sure that the correct firmware is downloaded.

		## src

		### Storage

		A utility to remember app permissions given by user.

		## Publishing

		[Follow instructions](../../docs/releases/npm-packages.md) how to publish @trezor package to npm registry.

files/bridge/latest.txt

files/coins.json

Sorry, the diff of this file is too big to display

New alerts