@mnci/cli 3.0.1 → 4.0.0

package/dist/cli.js

@@ -1538,7 +1538,23 @@ var FORMATTED_LANGUAGES = [
   "yaml",
   "markdown",
   "css",
-  "html"
+  "html",
+  // TOML is here for PARSING, not formatting, and the distinction is measured
+  // rather than assumed: `eslint --fix` leaves a badly-laid-out `.toml`
+  // byte-identical (the TOML block is `flat/base`, parser only — `flat/standard`
+  // reported six errors on the `pyproject.toml` mnci itself generates), but it
+  // DOES report `Parsing error: ...` on a malformed one.
+  //
+  // So the entry buys two things. `eslint.validate` gains toml, so a broken
+  // `pyproject.toml` is flagged in the editor rather than at the next CI run.
+  // And pinning the formatter to ESLint means format-on-save does nothing to the
+  // file instead of handing it to whichever TOML formatter the user happens to
+  // have installed — the same reasoning as every other entry here: nothing
+  // reformats against an opinion no gate checks.
+  //
+  // Impossible under the Prettier stack, which is why it is only here now:
+  // `npx prettier` on a `.toml` exits with "No parser could be inferred".
+  "toml"
 ];
 function vscodeSettings() {
   const formatter = "dbaeumer.vscode-eslint";
@@ -1685,7 +1701,7 @@ function poolBlock(agent) {
   return /^(?:ubuntu|windows|macos)-/i.test(agent) ? `  vmImage: ${agent}` : `  name: ${agent}`;
 }
 function azurePipelinesYaml(agent, variableGroup, pythonPublishUrl2, registryKind = "azure-artifacts") {
-  const onMain = "and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'), eq(variables['Build.SourceBranchName'], 'main'))";
+  const onMain = "and(succeeded(), in(variables['Build.Reason'], 'IndividualCI', 'BatchedCI'), eq(variables['Build.SourceBranchName'], 'main'))";
   const [npmAuthName, npmAuthValue] = npmAuthEnvVariable(registryKind, (name) => `$(${name})`);
   return `name: monorepo-ci-$(Date:yyyyMMdd)$(Rev:.r)