@tigerconnect/web-component-library - npm Package Compare versions

Comparing version 2.1.2-ms.beta.3 to 2.2.0

package.json

		{
		"name": "@tigerconnect/web-component-library",
		"version": "2.1.2-ms.beta.3",
		"version": "2.2.0",
		"description": "a shared component library for tc projects",
		@@ -5,0 +5,0 @@ "main": "lib/index.esm.js",

README.MD

		@@ -59,8 +59,9 @@ # Web Component Library

		1. Bump the package.json version higher than what is currently published, follow proper semantic
		versioning, and document the changes in CHANGELOG.md.
		2. Run `npm run deploy`. The command will run `npm run build` and then `npm publish`.
		1. First merge your feature work without any changes to the package version. You should document the changes in CHANGELOG.md under the `Unreleased` section.
		2. After merging your feature work, create a new PR that increments the package.json version (following proper semantic versioning) higher than what is currently published. Name the branch in the format `feature/major.minor.patch`. Move what is in `Unreleased` heading into `Released` under a new version and publish date header.
		3. Merge the version PR.
		4. Pull down latest master and locally run `npm run deploy`. The command will run `npm run build` and then `npm publish`.
		- This command will also build and deploy the latest Storybook application to
		[GitHub Pages](https://tigertext.github.io/web-component-library/).
		3. Update any repo using this package to have the newly published version and reinstall
		4. Update any repo using this package to have the newly published version and reinstall
		respectively.
		@@ -67,0 +68,0 @@

New alerts