@leverege/build-tools 2.39.0-beta.1 → 2.39.0-beta.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/refresh-npm-token.mjs +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leverege/build-tools",
3
- "version": "2.39.0-beta.1",
3
+ "version": "2.39.0-beta.2",
4
4
  "description": "A collection of build / support tools for Leverege developers",
5
5
  "main": "index.js",
6
6
  "repository": {
package/src/refresh-npm-token.mjs CHANGED
@@ -70,8 +70,8 @@ const sections = [
70
70
  This tool helps you retrieve an npmrc file stored in a secret within a GCP
71
71
  Secret Manager. It enables NPM administrators to manage a single NPM token
72
72
  for use by a development team. The tool checks the age of your local ~/.npmrc
73
- file, and if it exceeds the specified --npmrc-age setting, it will fetch the secret,
74
- overwriting the existing ~/.npmrc file.
73
+ file, and if it exceeds the specified --npmrc-age setting, it will fetch the
74
+ secret, overwriting the existing ~/.npmrc file.
75
75
 
76
76
  This tool may be invoked directly from the command line, or from scripts in
77
77
  the build-tools repository. For example, helmup will invoke this command for