chore: bump version

[tcely]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Bump version to 0.2.1

📦 Other

Walkthroughs

Description

• Update version from 0.2.0 to 0.2.1
• Update action references in README examples
• Bump package.json version number

Diagram

flowchart LR
  A["Version 0.2.0"] -- "bump" --> B["Version 0.2.1"]
  B -- "update" --> C["README examples"]
  B -- "update" --> D["package.json"]

Loading

File Changes

1. package.json ⚙️ Configuration changes +1/-1

Update package version to 0.2.1

• Update version field from 0.2.0 to 0.2.1

package.json

---

2. README.md 📝 Documentation +3/-3

Update action version references in examples

• Update action reference from v0.2.0 to v0.2.1 in three workflow examples
• Maintains consistency across all documented usage examples

README.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Cache invalidated by version 🐞 Bug ➹ Performance

Description

This PR changes only package.json’s version, but the composite action’s cache key hashes
package.json, so upgrading to v0.2.1 will force a cache miss and rebuild. This adds avoidable
install/build time for users when no dependencies or source inputs changed.

Code

package.json[3]

+  "version": "0.2.1",

Evidence

The cache key is derived from a hash over a temporary directory that explicitly includes
package.json, so any change to the package.json file (including version-only) changes the hash and
invalidates the cache. This PR modifies package.json’s version, thus guaranteeing a new cache key
and rebuild on the first run for v0.2.1.

package.json[1-6]
action.yml[38-56]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The composite action’s compiled-binary cache key includes a hash of `package.json`, so a version-only bump changes the cache key and forces a rebuild.

## Issue Context
This release PR updates only the `version` field in `package.json`, but `action.yml` copies `package.json` into the hash input set used by `hashFiles(...)` for the cache key.

## Fix Focus Areas
- action.yml[38-56]

### Suggested direction
- Remove `package.json` from the files copied into `.remote-action-hashFiles` and instead hash only inputs that affect the binary/deps (e.g., `src/**` and `bun.lock`).
- Alternatively, compute the cache key directly from `hashFiles('src/**', 'bun.lock')` and drop the temporary copy step entirely.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more