aboutsummaryrefslogtreecommitdiffstats
path: root/RELEASING_RAILS.md
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2019-05-12 11:59:14 +0200
committerXavier Noria <fxn@hashref.com>2019-05-12 12:00:03 +0200
commit65f9e0c4bbc56f208cb6b2329d890c6d9935da1d (patch)
tree4878acf31457eb8163fbee0d200dd166fc3bba52 /RELEASING_RAILS.md
parentb1c917ee2fdaa452aeb52904db0d254d85285380 (diff)
downloadrails-65f9e0c4bbc56f208cb6b2329d890c6d9935da1d.tar.gz
rails-65f9e0c4bbc56f208cb6b2329d890c6d9935da1d.tar.bz2
rails-65f9e0c4bbc56f208cb6b2329d890c6d9935da1d.zip
NPM -> npm [ci skip]
According to https://www.npmjs.com/.
Diffstat (limited to 'RELEASING_RAILS.md')
-rw-r--r--RELEASING_RAILS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASING_RAILS.md b/RELEASING_RAILS.md
index d2d7a771bc..bc39e2313d 100644
--- a/RELEASING_RAILS.md
+++ b/RELEASING_RAILS.md
@@ -125,7 +125,7 @@ guide. You can generate keys with the GPG suite from here: https://gpgtools.org.
Run `rake changelog:header` to put a header with the new version in every
CHANGELOG. Don't commit this, the release task handles it.
-Run `rake release`. This will populate the gemspecs and NPM package.json with
+Run `rake release`. This will populate the gemspecs and npm package.json with
the current RAILS_VERSION, commit the changes, tag it, and push the gems to
rubygems.org.