Skip to content

Commit 03e3511

Browse files
authored
Merge pull request #26 from conveyal/dev
New release
2 parents 13a1345 + 5e9cb06 commit 03e3511

File tree

5 files changed

+5799
-4793
lines changed

5 files changed

+5799
-4793
lines changed

.travis.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ cache:
44
notifications:
55
email: false
66
node_js:
7-
- '8'
7+
- '10'
88
after_success:
99
- npm run semantic-release
1010
branches:

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,12 @@ after_success:
9292
- semantic-release --prepare @conveyal/maven-semantic-release --publish @semantic-release/github,@conveyal/maven-semantic-release --verify-conditions @semantic-release/github,@conveyal/maven-semantic-release --verify-release @conveyal/maven-semantic-release --use-conveyal-workflow --dev-branch=dev --disable-snapshot-skip-ci --disable-final-skip-ci
9393
```
9494

95+
If you use the conveyal workflow just the updated `pom.xml` will be part of the commit. To add more files to the commit (e.g. a CHANGELOG.md generated by a different plugin) you can specify those via the parameter `--additionalFilesToCommit`. This parameter accepts a list of filenames and will include them in the commit. Example:
96+
```
97+
after_success:
98+
- semantic-release --prepare @conveyal/maven-semantic-release --publish @semantic-release/github,@conveyal/maven-semantic-release --verify-conditions @semantic-release/github,@conveyal/maven-semantic-release --verify-release @conveyal/maven-semantic-release --use-conveyal-workflow --dev-branch=dev --additionalFilesToCommit CHANGELOG.md,readme.txt
99+
```
100+
95101
#### before_install
96102

97103
Be sure to include the import of your signing keys. If you followed everything correctly in step 4 you should have something like the following added to your .travis.yml file:
@@ -132,3 +138,5 @@ Create a Github token that will be used to make commits and create releases. Ad
132138
## Which `mvn` will be used
133139

134140
This plugin uses the `mvn` command in your `PATH`. If you have [maven-wrapper script](https://github.com/takari/maven-wrapper) at the project root directory, this plugin will use that instead.
141+
142+

lib/git.js

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,12 @@ async function saveChangesToPomXml (context, versionStr) {
122122
logger.log('INFO: no multi-project pom.xml files found to add to commit')
123123
}
124124

125+
if (options.additionalFilesToCommit !== undefined && options.additionalFilesToCommit.length > 0) {
126+
logger.log('adding additional files to commit: ' + options.additionalFilesToCommit)
127+
const additionalFiles = options.additionalFilesToCommit.split(',')
128+
await add(additionalFiles, execaOpts)
129+
}
130+
125131
logger.log('committing changes')
126132
await commit(commitMessage, execaOpts)
127133
process.stdout.write('\n')

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@
2424
"xml2js-es6-promise": "^1.1.1"
2525
},
2626
"devDependencies": {
27-
"mastarm": "^4.1.0",
27+
"mastarm": "^5.1.3",
2828
"semantic-release": "^15.12.3"
2929
},
3030
"peerDependencies": {

0 commit comments

Comments
 (0)