apify-test-tools 0.10.2-beta.1 → 0.10.2-beta.11

package/.github/scripts/check-major-tag-refs.mjs

@@ -1,72 +0,0 @@
-#!/usr/bin/env node
-// Fails if any reference to this repo's own reusable workflows or composite actions points at a
-// different tag than MAJOR_TAG in _move_major_tag.yaml.
-//
-// `uses:` cannot take an expression ("You cannot use contexts or expressions in this keyword"), so
-// the tag consumers pin is repeated literally in every self-reference, in the commented examples,
-// and in the README snippets people copy. Bumping the major means editing all of them by hand.
-//
-// Missing one is quiet in the worst case: right after a bump both the old and new tags exist, so a
-// workflow called at the new tag happily pulls the composite action from the old one and runs a
-// stale version of it. Nothing fails, the behaviour is just wrong.
-
-import fs from 'node:fs';
-import path from 'node:path';
-
-const ROOT = path.resolve(import.meta.dirname, '../..');
-const TAG_SOURCE = '.github/workflows/_move_major_tag.yaml';
-const REVIEW_WORKFLOW = '.github/workflows/public_review.yaml';
-
-// Every place a ref into this repo can appear: live `uses:`, commented examples, README snippets.
-const SEARCH_PATHS = ['.github', 'README.md', 'CONTRIBUTING.md'];
-
-const read = (rel) => fs.readFileSync(path.join(ROOT, rel), 'utf8');
-
-const expected = read(TAG_SOURCE).match(/^\s*MAJOR_TAG:\s*(\S+)\s*$/m)?.[1];
-if (!expected) {
-    console.error(`Could not find MAJOR_TAG in ${TAG_SOURCE}.`);
-    process.exit(1);
-}
-
-const walk = (rel) => {
-    const abs = path.join(ROOT, rel);
-    if (!fs.statSync(abs).isDirectory()) return [rel];
-    return fs.readdirSync(abs).flatMap((entry) => walk(path.join(rel, entry)));
-};
-
-const problems = [];
-
-// Self-references, e.g. `uses: apify/apify-test-tools/.github/workflows/public_pr-build-test.yaml@workflows-v0`.
-// The ref charset stops at a backtick or quote so a ref quoted in prose isn't captured with its
-// punctuation; git refnames cannot end in a dot, so a sentence-final one is trimmed.
-const SELF_REF = /apify\/apify-test-tools\/\.github\/\S*?@([A-Za-z0-9._/-]+)/g;
-for (const file of SEARCH_PATHS.flatMap(walk)) {
-    read(file)
-        .split('\n')
-        .forEach((line, i) => {
-            for (const [match, rawRef] of line.matchAll(SELF_REF)) {
-                const ref = rawRef.replace(/\.+$/, '');
-                if (ref !== expected) {
-                    problems.push(`${file}:${i + 1}: ${match.trim()} — expected @${expected}`);
-                }
-            }
-        });
-}
-
-// review.yaml fetches its prompt from this repo by ref rather than by `uses:`, so it drifts the
-// same way: released workflows would read instructions from some other commit.
-const promptRef = read(REVIEW_WORKFLOW).match(/prompt-ref:\s*\n\s*default:\s*(\S+)/)?.[1];
-if (!promptRef) {
-    problems.push(`${REVIEW_WORKFLOW}: could not read the prompt-ref default.`);
-} else if (promptRef !== expected) {
-    problems.push(`${REVIEW_WORKFLOW}: prompt-ref default is ${promptRef} — expected ${expected}`);
-}
-
-if (problems.length > 0) {
-    console.error(`MAJOR_TAG is ${expected}, but these disagree:\n`);
-    for (const problem of problems) console.error(`  ${problem}`);
-    console.error(`\nUpdate them, or change MAJOR_TAG in ${TAG_SOURCE}.`);
-    process.exit(1);
-}
-
-console.log(`All references to this repo point at @${expected}.`);

package/.github/scripts/check-package-version-bump.mjs

@@ -1,74 +0,0 @@
-#!/usr/bin/env node
-// Reads changed file paths on stdin (one per line) and fails if a PR changes both a consumer-facing
-// workflow and the package code it calls, without repinning in workflows-package-version.
-//
-// The case this catches: a workflow starts using a CLI feature from the same PR. On merge the tag
-// moves, the workflow goes live, and it calls something that is not on npm yet — breaking every
-// consumer's CI at once. Pinning the unreleased version instead holds the tag until it publishes.
-//
-// It deliberately only looks at one PR. A workflow could also start depending on package code that
-// landed in an *earlier*, still-unreleased PR, which this will not see — that needs someone to ship
-// a breaking CLI change and then sit on it unreleased, and catching it means flagging every workflow
-// edit made while any package change is unreleased, which is far more noise than the case is worth.
-
-const PUBLIC_WORKFLOW = /^\.github\/workflows\/public_.*\.ya?ml$/;
-// The composite action is consumer-facing too, and it is what installs the package.
-const PUBLIC_ACTION = /^\.github\/actions\//;
-// What `npx apify-test-tools ...` runs, and the library the platform tests import.
-const PACKAGE_CODE = /^(bin\/|lib\/|index\.ts$)/;
-const PIN_FILE = '.github/workflows-package-version';
-const OVERRIDE_LABEL = 'no-version-bump-needed';
-
-const changed = await new Promise((resolve) => {
-    let buffer = '';
-    process.stdin.setEncoding('utf8');
-    process.stdin.on('data', (chunk) => (buffer += chunk));
-    process.stdin.on('end', () =>
-        resolve(
-            buffer
-                .split('\n')
-                .map((l) => l.trim())
-                .filter(Boolean),
-        ),
-    );
-});
-
-const publicSurface = changed.filter((f) => PUBLIC_WORKFLOW.test(f) || PUBLIC_ACTION.test(f));
-const packageCode = changed.filter((f) => PACKAGE_CODE.test(f));
-const versionRepinned = changed.includes(PIN_FILE);
-
-if (publicSurface.length === 0 || packageCode.length === 0) {
-    console.log('No consumer-facing workflow and package change in the same PR; nothing to check.');
-    process.exit(0);
-}
-
-if (versionRepinned) {
-    console.log(`Both sides changed and ${PIN_FILE} was repinned. The tag will hold until that version ships.`);
-    process.exit(0);
-}
-
-if (
-    (process.env.PR_LABELS ?? '')
-        .split(',')
-        .map((l) => l.trim())
-        .includes(OVERRIDE_LABEL)
-) {
-    console.log(`Both sides changed without a version bump, allowed by the "${OVERRIDE_LABEL}" label.`);
-    process.exit(0);
-}
-
-console.error(`This PR changes consumer-facing workflows and the package code they call:
-
-  workflows: ${publicSurface.join(', ')}
-  package:   ${packageCode.join(', ')}
-
-On merge the tag moves and those workflows go live immediately, against whatever is on npm today.
-If they rely on anything from the package change in this PR, that is not published yet and every
-consumer's CI breaks.
-
-If they do rely on it, set ${PIN_FILE} to the version that will contain it. The tag is then held
-until you cut that release, and moves on its own once it is published.
-
-If they do not rely on it — the two changes just happen to be in one PR — add the
-"${OVERRIDE_LABEL}" label.`);
-process.exit(1);

package/.github/workflows-package-version

@@ -1 +0,0 @@
-0.11.0