@mnci/cli 4.2.0 → 4.2.1

package/dist/cli.js

@@ -499,7 +499,7 @@ var ESLINT_PEER_OVERRIDES = {
   // both — and forcing those to v5 breaks them. So the blast radius is one
   // dependency edge per named parent, and a test asserts there is no top-level
   // entry.
-  "nx": { "brace-expansion": "^5.0.9" },
+  "nx": { "brace-expansion": "^5.0.9", "smol-toml": "^1.7.1" },
   "@nx/js": { "brace-expansion": "^5.0.9" },
   "@nx/eslint": { "brace-expansion": "^5.0.9" },
   "@nx/eslint-plugin": { "brace-expansion": "^5.0.9" },
@@ -792,8 +792,8 @@ function nugetConfigContent(registry, scope) {
      nuget.org-issued API key, a credential mnci collects nowhere (the same
      gap Python's PyPI publish has for this same registry choice). A
      csharp-lib is still versioned and tagged; run "dotnet nuget push"
-     yourself with your own key, or regenerate with --registry
-     azure-artifacts. -->
+     yourself with your own key, or regenerate choosing the azure-artifacts
+     registry instead. -->
 <configuration>
   <packageSources>
     <clear />
@@ -2004,7 +2004,7 @@ class CsharpVersionActions extends VersionActions {
     if (!VERSION_TAG.test(contents)) {
       throw new Error(\`Could not find a <Version> element in \${manifestPath}\`)
     }
-    tree.write(manifestPath, contents.replace(VERSION_TAG, \`<Version>\${newVersion}</Version>\`))
+    tree.write(manifestPath, contents.replace(VERSION_TAG, () => \`<Version>\${newVersion}</Version>\`))
 
     return [\`Updated \${manifestPath} to version \${newVersion}\`]
   }