Merge pull request #19 from OskarAhl/oskar/remove_postProcess_transla…

…tions

oskar/remove_postProcess_translations

Gruntfile.js

@@ -12,11 +12,5 @@ module.exports = function (grunt) {
             scope  : 'devDependencies',
             config : require('./package.json'),
         },
-        postProcess: function(config) {
-            // release to translations automatically after releasing to staging, since staging release is always with 'cleanup'
-            if (global.release_target === 'staging') {
-                config.aliases.release.push('shell:release_translations');
-            }
-        },
     });
 };

README.md

@@ -87,7 +87,7 @@ grunt release --{release type}=1 [--cleanup] [--reset]
 
 ### Parameters:
 - `{release type}` (mandatory)
-  - Should be one of `staging`, `production`, `translations`, `nex_beta`, `nex_production`.
+  - Should be one of `staging`, `production`, `translations`.
   - In order to prevent accidentally releasing to the wrong target, it is mandatory to provide one of these parameters.
   - Your remote origin will be checked to be the correct target of the given parameter.
   - Your current branch will be checked to be the correct branch of the given parameter.

build/aliases.yaml

@@ -61,4 +61,3 @@ release:
   - 'shell:reset_ghpages'
   - 'shell:make_cname'
   - 'gh-pages:main'
-  - 'shell:trigger_tests'