17cb550539
Problem: Targeting only the latest version of Node.js and the latest LTS means that we have a sort of rolling backward-compatibility that's hard to reason about. If we break compatibility, we should release those changes as a major version, but the current strategy makes it difficult to tell exactly when we're breaking compatibility. Solution: Specify the exact Node.js versions that we want to support in `package.json` and add the specific tests to `.travis.yml`. In the future we can break compatibility if it's helpful but we'll have to do so explicitly and release the change as a major version.
22 lines
390 B
YAML
22 lines
390 B
YAML
# Use Node.js configuration.
|
|
language: node_js
|
|
|
|
# Test the latest and LTS releases >= LTS Dubnium (10).
|
|
node_js:
|
|
- lts/dubnium
|
|
- lts/erbium
|
|
- node
|
|
|
|
# All of the operating systems!
|
|
# Note: Windows support is iffy.
|
|
os:
|
|
- linux
|
|
- osx
|
|
- windows
|
|
|
|
# Don't build arbitrary branches, just pull requests + master + semver tags.
|
|
branches:
|
|
only:
|
|
- master
|
|
- "/^v\\d+\\.\\d+\\.\\d+$/"
|