@codastic/release
Advanced tools
Comparing version 1.2.0 to 1.3.0
@@ -45,3 +45,6 @@ #!/usr/bin/env node | ||
' --target-branch (optional) (default: MAJOR.x) The branch where the release will be pushed to.', | ||
' --build-command (optional) Run the build to be able to include the new version from package.json' | ||
[ | ||
' --build-command (optional) Run the build to be able to include the new version from package.json.', | ||
'Also adds the built files if they are not ignored.' | ||
].join(' ') | ||
].join('\n')); | ||
@@ -109,3 +112,6 @@ process.exit(1); | ||
'# Run the build script', | ||
`${argv['build-command']} &&` | ||
`${argv['build-command']} &&`, | ||
'# Add built changes', | ||
'git add --all &&', | ||
`git diff-index --quiet HEAD || git commit -m 'Added built files to verion v${newVersion}'` | ||
]; | ||
@@ -112,0 +118,0 @@ |
### v1.3.0 / 2018-02-28 11:11:17 | ||
- Add files built via `--build-command` if not ignored (i: Chris Ranz, r: Mario Volke, c: bc55a82) | ||
### v1.2.0 / 2018-01-16 12:33:09 | ||
@@ -3,0 +7,0 @@ |
{ | ||
"name": "@codastic/release", | ||
"version": "1.2.0", | ||
"version": "1.3.0", | ||
"description": "A collection of release and changelog management script you can easily use via NPM.", | ||
@@ -5,0 +5,0 @@ "scripts": { |
@@ -72,3 +72,3 @@ # @codastic/release | ||
- `--build-command`: *(optional)* Run the build to be able to include the new version from `package.json` (e.g `--build-command='npm run build' ./"`). | ||
- `--build-command`: *(optional)* Run the build to be able to include the new version from `package.json` (e.g `--build-command='npm run build' ./"`). Also adds and commits the build files if they are not ignored. | ||
@@ -75,0 +75,0 @@ ## release-github |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
522
24359
11
4