apify-test-tools 0.10.2-beta.14 → 0.10.2-beta.15

package/.github/workflows/public_stale-issues.yaml

@@ -0,0 +1,51 @@
+name: Close stale issues
+
+on:
+    workflow_call:
+        inputs:
+            stale-months:
+                description: Months without activity before warning issue owners (one month = 30 days). Issues close 30 days after the warning.
+                type: number
+                default: 6
+
+jobs:
+    staleIssues:
+        runs-on: ubuntu-latest
+        timeout-minutes: 30
+        permissions:
+            issues: write
+        concurrency:
+            group: stale-issues-${{ github.repository }}
+            cancel-in-progress: false
+        steps:
+            - name: Convert months to days
+              id: threshold
+              uses: actions/github-script@v9
+              env:
+                  STALE_MONTHS: ${{ inputs.stale-months }}
+              with:
+                  script: |
+                      const months = Number(process.env.STALE_MONTHS);
+                      if (!Number.isSafeInteger(months) || months < 1 || !Number.isSafeInteger(months * 30)) {
+                          throw new Error('stale-months must be a positive whole number whose day count is a safe integer.');
+                      }
+                      if (months > 12) {
+                          throw new Error('stale-months must be less than or equal to 12.');
+                      }
+                      return months * 30;
+
+            - name: Warn and close stale issues
+              uses: actions/stale@v11
+              with:
+                  days-before-issue-stale: ${{ steps.threshold.outputs.result }}
+                  days-before-issue-close: 30
+                  days-before-pr-stale: ${{ steps.threshold.outputs.result }}
+                  days-before-pr-close: 30
+                  stale-issue-label: stale
+                  stale-issue-message: >-
+                      This issue has had no activity for ${{ inputs.stale-months }} month(s).
+                      It will be closed as not planned in 30 days unless it is updated or commented on.
+                  close-issue-message: Closed as not planned after 30 days without activity following the stale warning.
+                  close-issue-reason: not_planned
+                  remove-stale-when-updated: true
+                  operations-per-run: 1000

package/CHANGELOG.md

@@ -16,6 +16,7 @@ All notable changes to this project will be documented in this file.
 - Support flexible secret passing methods in workflows ([#225](https://github.com/apify/apify-test-tools/pull/225)) ([22f7e80](https://github.com/apify/apify-test-tools/commit/22f7e807ca3949656c15b79f848a192d71b15946)) by [@metalwarrior665](https://github.com/metalwarrior665), closes [#205](https://github.com/apify/apify-test-tools/issues/205)
 - [**breaking**] Require env vars of test versions in sync with the default version ([#217](https://github.com/apify/apify-test-tools/pull/217)) ([a2481dd](https://github.com/apify/apify-test-tools/commit/a2481ddf09004308cb54e49b783c8b21a25dcbe4)) by [@metalwarrior665](https://github.com/metalwarrior665)
 - Add impact & priority assessment to claude investigator ([#216](https://github.com/apify/apify-test-tools/pull/216)) ([fd16622](https://github.com/apify/apify-test-tools/commit/fd16622b910ec6e9b5515ea0bd26b0a41c22bd23)) by [@foxt451](https://github.com/foxt451), closes [#208](https://github.com/apify/apify-test-tools/issues/208)
+- Stale issue/pr workflow ([#236](https://github.com/apify/apify-test-tools/pull/236)) ([aff1fa7](https://github.com/apify/apify-test-tools/commit/aff1fa778adb846a60fdacdd26aa13a71729613d)) by [@JuanGalilea](https://github.com/JuanGalilea), closes [#35](https://github.com/apify/apify-test-tools/issues/35)
 
 ### 🐛 Bug Fixes
 

package/CONTRIBUTING.md

@@ -73,7 +73,7 @@ You need to run `npm run build` inside `apify-test-tools` repo everytime you wan
 ## Reusable workflows
 
 The `public_`-prefixed workflows are the ones consumer repos call: `public_pr-build-test`,
-`public_platform-tests`, `public_push-build-latest`, `public_claude`, `public_review` and
+`public_platform-tests`, `public_push-build-latest`, `public_claude`, `public_review`, `public_stale-issues` and
 `public_platform-tests-claude-investigate-and-fix`. They live here because they call this package's
 CLI, so a change to both is one PR. GitHub only reads workflow files at the top level of
 `.github/workflows`, so they sit next to this repo's own CI, and the prefix is what separates the

package/README.md

@@ -210,7 +210,7 @@ The workflows take every change straight to production, with tests in between:
 These are GitHub Actions workflows. On another CI platform, build the same flow with the [CLI](docs/cli.md).
 
 Add these files to `.github/workflows` in your repo. They call the reusable workflows in this repo, pinned at the
-`@workflows-v0` major tag — never at `@master`. Every input, the optional Claude workflows, and how the tag moves are
+`@workflows-v0` major tag — never at `@master`. Every input, the optional Claude workflows, stale issue closer, and how the tag moves are
 in the [Workflow API](docs/workflows.md).
 
 ### `pr-build-devel-test.yaml`

package/docs/workflows.md

@@ -26,6 +26,7 @@ The build, release and test workflows below list the CLI commands they run.
 | [`public_platform-tests.yaml`](#public_platform-testsyaml)                                                       | `schedule`                          | Runs platform tests against the released builds and reports results to Slack     |
 | [`public_review.yaml`](#public_reviewyaml)                                                                       | `pull_request` (labeled)            | Claude reviews the PR against the shared guidelines                              |
 | [`public_claude.yaml`](#public_claudeyaml)                                                                       | issue and PR comments, issue labels | Claude acts on `@claude` mentions                                                |
+| [`public_stale-issues.yaml`](#public_stale-issuesyaml)                                                           | `schedule`                          | Warns owners of inactive issues, then closes them a month later                  |
 | [`public_platform-tests-claude-investigate-and-fix.yaml`](#public_platform-tests-claude-investigate-and-fixyaml) | after a failed platform test job    | Claude investigates a failing platform test, opens an issue, and tries to fix it |
 
 All of them run on `ubuntu-latest` with Node.js 24. The ones that need the repo's dependencies install them with
@@ -298,6 +299,44 @@ jobs:
             TESTER_APIFY_TOKEN: ${{ secrets.TESTER_APIFY_TOKEN }}
 ```
 
+## `public_stale-issues.yaml`
+
+Optional. Wraps [`actions/stale`](https://github.com/actions/stale) to warn on inactive GitHub issues, then close them
+as **not planned** 30 days later if still inactive. Locked issues are skipped. Pull requests use the same stale and
+close thresholds, with the `Stale` label and no warning or closing comments.
+
+| Input          | Type   | Default | Description                                                          |
+| -------------- | ------ | ------- | -------------------------------------------------------------------- |
+| `stale-months` | number | `6`     | Optional whole number of inactive months (1–12); one month = 30 days |
+
+```yaml
+name: Close stale issues
+
+on:
+    schedule:
+        - cron: '0 3 * * *'
+    workflow_dispatch:
+
+jobs:
+    staleIssues:
+        permissions:
+            issues: write
+        uses: apify/apify-test-tools/.github/workflows/public_stale-issues.yaml@workflows-v0
+        with:
+            stale-months: 6
+```
+
+With `stale-months: 6`, an issue is labeled `stale` and warned after 180 days without activity, then closed after
+another 30 inactive days. Existing older issues also get the full 30-day warning when adopting the workflow.
+Actions happen on a scheduled run after the threshold; large backlogs are processed over successive runs.
+
+The warning comment uses [GitHub's normal issue notifications](https://docs.github.com/en/subscriptions-and-notifications/reference/inbox-filters),
+including notifications for assigned issues, subject to each user's notification settings. It does not add explicit
+@mentions. Subsequent activity causes `actions/stale` to remove the stale label and restart the inactivity period.
+
+The caller must grant `issues: write` as shown above. The workflow uses the automatic `GITHUB_TOKEN`; no additional
+secrets, checkout, project dependencies, or Apify configuration are needed.
+
 ## Secrets
 
 The workflows take two kinds of secrets:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "apify-test-tools",
-  "version": "0.10.2-beta.14",
+  "version": "0.10.2-beta.15",
   "type": "module",
   "description": "TBD",
   "repository": {