This repository has been archived by the owner on Mar 31, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #198 from pxblue/dev
Publish 6.1.0
- Loading branch information
Showing
19 changed files
with
112 additions
and
197 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
* @emclaug2 @joebochill @huayunh @daileytj |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,27 @@ | ||
# Publishing Instructions | ||
|
||
To update the version number, edit the version in `angular/package.json`. | ||
## Automatic Publishing | ||
|
||
To publish a new package through NPM, run the following commands from the root folder: | ||
This package is published to NPM automatically by CircleCI when code is merged into the `dev` or `master` branches. To publish a new version, simply update the version in `package.json` and merge your code into the appropriate branch. | ||
|
||
```sh | ||
npm publish --tag <alpha | beta> | ||
``` | ||
- The `dev` branch will publish versions marked as `alpha` or `beta`. | ||
- The `master` branch will publish any version (`alpha`, `beta`, or `latest`). | ||
In both cases, the code will only be published if the version number differs from the current version published under the respective dist tag. | ||
|
||
Alternatively, you can run: | ||
## Manually Publishing | ||
|
||
If you need to publish a package manually, you can run the following commands from the root folder: | ||
|
||
```sh | ||
yarn publish:package | ||
``` | ||
|
||
which will automatically look at the version in `angular/package.json` and determine whether to publish an alpha, beta, or latest package. For this command to work, you must have an NPM token configured in your environment variables or you can perform a login prior to executing the publish command via `npm adduser && yarn publish:package`. | ||
The publishing script will look at the version in the `package.json` and automatically determine whether to publish an alpha, beta, or latest package. | ||
|
||
For this command to work, you must have an NPM token configured in your environment variables or you can perform a login prior to executing the publish command via: | ||
|
||
```sh | ||
npm adduser && yarn publish:package | ||
``` | ||
|
||
> The above command should only be run manually for `alpha` or `beta` packages. Latest packages should only be published automatically by CircleCI once the code has been merged into the master branch. | ||
> Publishing manually should only be done for `alpha` or `beta` packages. The command will work for `latest` packages, but this should be avoided except in rare situations where the automatic publishing functionality is not working in CircleCI. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,7 +2,7 @@ | |
"name": "@pxblue/angular-themes", | ||
"author": "PX Blue <[email protected]>", | ||
"license": "BSD-3-Clause", | ||
"version": "6.0.3", | ||
"version": "6.1.0", | ||
"description": "Angular themes for PX Blue applications", | ||
"scripts": { | ||
"initialize": "bash scripts/initializeSubmodule.sh", | ||
|
@@ -11,7 +11,7 @@ | |
"link:themes": "bash ./scripts/linkThemes.sh", | ||
"test": "bash ./scripts/buildTest.sh", | ||
"prettier": "prettier \"**/**.{css,scss,html,md}\" --write", | ||
"publish:package": "bash ./scripts/publish.sh", | ||
"publish:package": "set npm_config_yes=true && npx -p @pxblue/publish pxb-publish", | ||
"precommit": "yarn initialize && yarn install:dependencies && yarn prettier && yarn test" | ||
}, | ||
"repository": { | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,29 @@ | ||
# Publishing Instructions | ||
|
||
To update the version number, edit the version in `react-native/package.json`. | ||
## Automatic Publishing | ||
|
||
To publish a new package through NPM, run the following commands from the root folder: | ||
This package is published to NPM automatically by CircleCI when code is merged into the `dev` or `master` branches. To publish a new version, simply update the version in `package.json` and merge your code into the appropriate branch. | ||
|
||
``` | ||
yarn build | ||
npm publish --tag <alpha | beta> | ||
``` | ||
- The `dev` branch will publish versions marked as `alpha` or `beta`. | ||
- The `master` branch will publish any version (`alpha`, `beta`, or `latest`). | ||
In both cases, the code will only be published if the version number differs from the current version published under the respective dist tag. | ||
|
||
Alternatively, you can run: | ||
## Manually Publishing | ||
|
||
If you need to publish a package manually, you can run the following commands from the root folder: | ||
|
||
```sh | ||
yarn build | ||
yarn publish:package | ||
``` | ||
|
||
which will automatically look at the version in `react-native/package.json` and determine whether to publish an alpha, beta, or latest package. For this command to work, you must have an NPM token configured in your environment variables or you can perform a login prior to executing the publish command via `npm adduser && yarn publish:package`. | ||
The publishing script will look at the version in the `package.json` and automatically determine whether to publish an alpha, beta, or latest package. | ||
|
||
For this command to work, you must have an NPM token configured in your environment variables or you can perform a login prior to executing the publish command via: | ||
|
||
```sh | ||
yarn build | ||
npm adduser && yarn publish:package | ||
``` | ||
|
||
> The above command should only be run manually for `alpha` or `beta` packages. Latest packages should only be published automatically by CircleCI once the code has been merged into the master branch. | ||
> Publishing manually should only be done for `alpha` or `beta` packages. The command will work for `latest` packages, but this should be avoided except in rare situations where the automatic publishing functionality is not working in CircleCI. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.