v0.2.5

Issues | Pull Requests | v0.2.4...v0.2.5

Features

#120 #121 Use ghcp managed by this action, meaning you don't need to install ghcp yourself anymore

v0.2.4

Issues | Pull Requests | v0.2.3...v0.2.4

Features

#79 Add read_checksum_token input to allow custom token for aqua update-checksum @iwata

This action didn't have any input to pass GitHub Access Tokens, so you needed to pass a GitHub Access Token via environment variable GITHUB_TOKEN.

e.g. https://github.com/aquaproj/update-checksum-workflow/blob/437067ad2fba9ba8ed8454cf207f2532432d4e28/.github/workflows/update-checksum.yaml#L142-L147

      - uses: aquaproj/update-checksum-action@0fef5fa12e81e046bb29078f76b99bb29fa4e696 # v0.2.3
        env:
          GITHUB_TOKEN: ${{steps.generate_token.outputs.token}}

But this action uses GitHub Access token for two purposes.

1. aqua update-checksum: It may access private registries and packages. contents: read
2. push a commit by ghcp: It may access a private repository contents: write

These two purposes requires different permissions and scopes.
Especially, contents:write for private registries and packages is undesirable.

As of v0.2.4, you can pass a GitHub access token for aqua update-checksum via the input read_checksum_token.
So, you can pass two different access tokens.

e.g.

      - uses: aquaproj/update-checksum-action@0fef5fa12e81e046bb29078f76b99bb29fa4e696 # v0.2.3
        with:
          read_checksum_token: ${{steps.generate_token.outputs.token}} # Token for `aqua update-checksum`
        env:
          GITHUB_TOKEN: ${{ github.token }} # Token for pushing a commit

read_checksum_token is optional. By default, AQUA_GITHUB_TOKEN or GITHUB_TOKEN is used.

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