2.0.10

What's Changed

• Bump @octokit/request-error from 5.0.1 to 5.1.1 in the npm_and_yarn group across 1 directory in #51
• Bump the npm_and_yarn group across 1 directory with 2 updates in #52
• Use correct property for getting API workflow failure by @hansmi in #54
• Fix typo in "GitHub" in API workflow status message by @hansmi in #53

New Contributors

• @hansmi made their first contribution in #54

Full Changelog: 2.0.9...2.0.10

2.0.9

What's Changed

• Dependany updates by @dependabot in #50

Full Changelog: 2.0.8...2.0.9

2.0.8

What's Changed

• added the ability to skip timeElapsed check by simply setting it to 0

Full Changelog: 2.0.7...2.0.8

2.0.7

What's Changed

• replace the default elapsed time value of 50 with 45 by @Han-Joon-Hyeok in #45

New Contributors

• @Han-Joon-Hyeok made their first contribution in #45

Full Changelog: 2.0.6...2.0.7

2.0.6

What's Changed

• feat: show elapsed date by @scarf005 in #43

New Contributors

• @scarf005 made their first contribution in #43

Full Changelog: 2.0.5...2.0.6

2.0.5

What's Changed

• Fixes: Action does not complete and causes the parent workflow to fail. (triggered by pull request from fork) #42
• Fixed warnings

Full Changelog: 2.0.4...2.0.5

2.0.4

What's Changed

• NPM Package bug fixes

Full Changelog: 2.0.3...2.0.4

2.0.3

What's Changed

• Bug fix: Support yml and yaml by matching before @ (#37) by @AlexanderOMara
• Reduced time_elapsed to 45 days to avoid GitHub from sending notification emails. Thanks to @rfay (#36) and @julienloizelet

Full Changelog: 2.0.2...2.0.3

2.0.2

What's Changed

• Adding parent workflow name to the output

Full Changelog: 2.0.1...2.0.2

2.0.1

What's Changed

Added multi workflow keepalive

Now you can keep multiple Github actions alive using a single keepalive workflow. Previously you had to add separate keepalive workflow to all the cronjob-triggered Github actions for this to happen.

Example

Let's assume that you have some build workflows:

• .github/workflows/build1.yml

name: Build 20

on:
  schedule:
    - cron: "0 0 * * *"

jobs:
  publish-npm:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "20"
          cache: "yarn"
      - run: yarn install --frozen-lockfile
      - run: yarn build

• .github/workflows/build2.yml

name: Build 19

on:
  schedule:
    - cron: "0 0 * * *"

jobs:
  publish-npm:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "19"
          cache: "yarn"
      - run: yarn install --frozen-lockfile
      - run: yarn build

You can now keep both of these workflows active using the following keepalive workflow code:
.github/workflows/keepalive.yml

name: Keepalive Workflow
on:
  schedule:
    - cron: "0 0 * * *"
permissions:
  actions: write
jobs:
  cronjob-based-github-action:
    name: Keepalive Workflow
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gautamkrishnar/keepalive-workflow@v2
        with:
          workflow_files: "build1.yml, build2.yml"
          time_elapsed: "0"

Result:

Other changes

• Fix readme to have permissions in correct place by @rfay in #26
• fix: typo in dummy commit config by @shihyuho in #28

New Contributors

• @rfay made their first contribution in #26
• @shihyuho made their first contribution in #2

Full Changelog: 2.0.0...2.0.1