New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@the-control-group/ui

Package Overview
Dependencies
Maintainers
1
Versions
59
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@the-control-group/ui - npm Package Compare versions

Comparing version 1.7.15 to 1.7.16

1

lib/index.js

@@ -0,1 +1,2 @@

// Make these available to import directly from the package root
export { default as Grid } from './elements/Grid/Grid';

@@ -2,0 +3,0 @@ export { default as FlexRow } from './elements/FlexRow/FlexRow';

2

package.json
{
"name": "@the-control-group/ui",
"version": "1.7.15",
"version": "1.7.16",
"description": "UI kit based on ReactJS for TCG projects",

@@ -5,0 +5,0 @@ "main": "lib/index.js",

@@ -13,5 +13,5 @@ [![npm (scoped)](https://img.shields.io/npm/v/@the-control-group/ui.svg?style=flat-square)](https://www.npmjs.com/package/@the-control-group/ui)

## Publish Release
It’s a standard NPM release process.
Make a new branch called `release/x.x.x` for w/e the version number is, then run `npm version <version#>` to update the package.json
Then merge that into master, create a git release, and run `npm publish`
And follow the semver pattern obviously
- Make a new branch called `release/x.x.x` for the version number
- run `npm version <major|minor|patch>` to automatically update `package.json`, `package-lock.json`, and create a git tag
- be sure to push the branch with the `--tags` option
- after merging into `master`, create a new release from the pushed tag and GitHub actions will publich to `npm` and GH package registry
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc