conda-forge / webservices-dispatch-action

a GitHub action to rerender conda-forge feedstocks
BSD 3-Clause "New" or "Revised" License
2 stars 9 forks source link

Bump gautamkrishnar/keepalive-workflow from 2.0.0 to 2.0.1 #63

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps gautamkrishnar/keepalive-workflow from 2.0.0 to 2.0.1.

Release notes

Sourced from gautamkrishnar/keepalive-workflow's releases.

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:

... (truncated)

Commits
  • beb8621 [skip-ci] Published 2.0.1
  • 4f4ff4b feat: added multi workflow keepalive
  • 6628cda Bump the npm_and_yarn group across 1 directory with 2 updates (#32)
  • 4c03ac4 add shihyuho as a contributor for doc (#29)
  • 56c0fa1 fix: typo in dummy commit config (#28)
  • 6112edb added docs to migrate, fixed: #27
  • 016168f added docs to migrate, fixed: #27
  • e51cc35 Fix readme to have permissions in correct place (#26)
  • See full diff in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)