@leverege/build-tools 2.57.1 → 2.57.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/hook-and-release/Config.mjs +6 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leverege/build-tools",
3
- "version": "2.57.1",
3
+ "version": "2.57.2",
4
4
  "description": "A collection of build / support tools for Leverege developers",
5
5
  "main": "index.js",
6
6
  "repository": {
package/src/hook-and-release/Config.mjs CHANGED
@@ -48,10 +48,15 @@ connection is made during the {yellow.bold npm install} phase, which will execut
48
48
 
49
49
  {yellow.bold "scripts": {
50
50
  ...
51
- "prepare": "hook-and-release",
51
+ "prepare": "[ $SKIP_PREPARE ] && exit 0 || hook-and-release",
52
52
  ...
53
53
  }
54
54
 
55
+ Note the {yellow SKIP_PREPARE} flag will be set in the docker-to-registry Dockerfile
56
+ template in order to avoid setting up the hooks during the image build
57
+ process. The hook is only relevant when doing local development and is
58
+ totally divorced from the image building process.
59
+
55
60
  The hook-and-release script can be invoked directly from the command line,
56
61
  typically for first-time initialization, or from the git hook scripts located
57
62
  in the .har subdirectory in the root of a repository. Running with the {yellow.bold --init}