-
Notifications
You must be signed in to change notification settings - Fork 1
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 #47 from MetroStar/CSG-632
CSG-632: Final Cleanup/Review of Comet Projects
- Loading branch information
Showing
6 changed files
with
50 additions
and
11 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
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,37 @@ | ||
# Releasing new versions of packages | ||
|
||
Note: currently full releases are tied to the main `comet-uswds` package. | ||
|
||
## Releasing a new version of comet-uswds | ||
|
||
1. Create a new release branch in the form of `comet-uswds-release-[MAJOR.MINOR.PATCH]` | ||
2. Create a PR into main (should only include package.json and package-lock.json) | ||
3. Once approved, merge the PR into main | ||
4. Navigate to the Releases GitHub page and create a new Draft release | ||
- Set tag and title to the version number | ||
- Click the Generate release notes button (update as needed) | ||
- Click Save draft | ||
5. Publish when ready | ||
6. Verify the Publish Package GitHub Action completes correctly | ||
7. Verify a new release is available in NPM | ||
|
||
## Releasing a new version of comet-data-viz, comet-extras, etc | ||
|
||
1. Create a new release branch in the form of `comet-data-viz-release-[MAJOR.MINOR.PATCH]` | ||
2. Create a PR into main (should only include package.json and package-lock.json) | ||
3. Once approved, merge the PR into main | ||
4. Open a terminal on your local machine and navigate to the root of the project | ||
5. Run a build for the specific package (example below): | ||
|
||
``` | ||
npm run build:comet-data-viz | ||
``` | ||
|
||
6. Publish the new package to NPM (example below): | ||
|
||
``` | ||
npm run publish:comet-data-viz | ||
``` | ||
|
||
7. Verify no errors in the terminal | ||
8. Verify a new release is available on NPM |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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