Flake Lock Update Workflow

Description

This repository provides Github Workflows ready to use to make sure that the flake.lock file in your repository stay up-to-date.

• Either by creating a pull-request
• Either by silently updating the repository flake.lock file.

Read more information about this feature on Github.

Usage

You can choose to use the latest release or the latest commit from the main branch.

I would personally suggest to use the latest branch version: main

Create an action file in .github/workflows/ with:

name: 'Update flake lock file'

on:
  # Uncomment this to enable manuel triggering
  # workflow_dispatch:
  schedule:
    - cron: '0 0 * * 1' # Every Monday at midnight, see https://crontab.guru/ for more examples

jobs:
  createPullRequest:
    uses: loophp/flake-lock-update-workflow/.github/workflows/upgrade-flakes.yaml@main

If you want to switch to the release, replace main with the latest release available in Github as such:

name: 'Update flake lock file'

on:
  # Uncomment this to enable manuel triggering
  # workflow_dispatch:
  schedule:
    - cron: '0 0 * * 1' # Every Monday at midnight, see https://crontab.guru/ for more examples

jobs:
  createPullRequest:
    uses: loophp/flake-lock-update-workflow/.github/workflows/upgrade-flakes.yaml@1.0.2

To have your flake.lock file updated silently, use:

name: 'Update flake lock file'

on:
  # Uncomment this to enable manuel triggering
  # workflow_dispatch:
  schedule:
    - cron: '0 0 * * 1' # Every Monday at midnight, see https://crontab.guru/ for more examples

jobs:
  createPullRequest:
    uses: loophp/flake-lock-update-workflow/.github/workflows/auto-upgrade-flakes.yaml@main

Contributing

Feel free to contribute by sending Github pull requests. I'm quite responsive :-)

If you can't contribute to the code, you can also sponsor me on Github.

Changelog

See CHANGELOG.md for a changelog based on git commits.

For more detailed changelogs, please check the release changelogs.