v0.2.3

Issues | Pull Requests | v0.2.2...v0.2.3

Fixes

#39 Stop using fromJSON

fromJSON causes a panic if the input isn't JSON. The panic makes the troubleshooting difficult.
Especially, if actions are nested you can't understand where and why the panic occurs.

So instad of fromJSON, we use == 'true' and != 'true'.

v0.2.2

Issues | Pull Requests | v0.2.1...v0.2.2

Fixes

#32 Fix a bug that action doesn't work well if working_directory isn't empty

v0.2.1

Issues | Pull Requests | v0.2.0...v0.2.1

Fixes

#30 Output error if ghcp isn't installed

v0.2.0

Issues | Pull Requests | v0.1.6...v0.2.0

⚠️ Breaking Changes

#26 Remove a reusable workflow

Please use https://github.com/aquaproj/update-checksum-workflow

Fixes

#28 Support updating aqua-checksums.json in a directory .?aqua, which is supported by aqua v1.33.0

v0.1.7-1

#28

What's Changed

• fix: remove a reusable workflow by @suzuki-shunsuke in #26
• chore(deps): update dependency aquaproj/aqua-renovate-config to v1.5.2 by @renovate in #27

Full Changelog: v0.1.6...v0.1.7-1

v0.1.6

Issues | Pull Requests | v0.1.5...v0.1.6

Features

#25 Add inputs to the reusable workflow

• prune
• working_directory

v0.1.5

Issues | Pull Requests | v0.1.4...v0.1.5

Features

#22 Add a reusable workflow

Workflow

Eample

name: update-aqua-checksum
on:
  pull_request:
    paths:
      - aqua.yaml
      - aqua-checksums.json
jobs:
  update-aqua-checksums:
    uses: aquaproj/update-checksum-action/.github/workflows/update-checksum.yaml@d0f60c5e83d035616de1e73d2b75f56b167f173e # v0.1.5
    permissions:
      contents: read
    with:
      aqua_policy_config: aqua-policy.yaml
      aqua_version: v1.32.3
    secrets:
      gh_app_id: ${{secrets.APP_ID}}
      gh_app_private_key: ${{secrets.APP_PRIVATE_KEY}}

v0.1.4

Issues | Pull Requests | v0.1.3...v0.1.4

Features

#21 Support aquaproj directory

aquaproj/aqua#1615

Fixes

#21 Fix a bug that it fails to update .aqua-checksums.json

v0.1.3

Issues | Pull Requests | v0.1.2...v0.1.3

Features

#20 Add an optional input skip_push

By default, this is false. If this is true, a commit isn't pushed to a remote branch.
This is useful when the permission contents: write is unavailable.

v0.1.2

Issues | Pull Requests | v0.1.1...v0.1.2

Bug Fixes

#18 #19 Support push event