chore(main): release 0.5.3

[github-actions]

🤖 I have created a release beep boop

0.5.3 (2026-05-18)

Bug Fixes

• rename workflow to release.yml to match npm trusted publisher (42efdca)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated Release Please PR bumping the package version from 0.5.2 to 0.5.3. The underlying fix (renaming the workflow file to release.yml to align with the npm trusted publisher config) landed in the previous commit; this PR only records the version bump and changelog entry.

• package.json and .release-please-manifest.json are updated to 0.5.3.
• CHANGELOG.md gains a new section documenting the workflow rename bug fix.

Confidence Score: 5/5

Safe to merge — purely mechanical version bump with no logic changes.

All three changed files are generated by Release Please and contain only version-string and changelog updates. There is no application code, configuration, or security-sensitive content touched by this PR.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from "0.5.2" to "0.5.3" — mechanical Release Please change.
CHANGELOG.md	New 0.5.3 section added noting the workflow rename fix; no issues found.
package.json	Package version bumped from "0.5.2" to "0.5.3" — mechanical Release Please change.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] --> B[Detect merged fix commit\n42efdca - rename workflow to release.yml]
    B --> C[Bump version\n0.5.2 → 0.5.3]
    C --> D[Update .release-please-manifest.json]
    C --> E[Update package.json]
    C --> F[Append CHANGELOG.md entry]
    D & E & F --> G[Open PR #38]
    G --> H{Merge}
    H --> I[Publish v0.5.3 to npm\nvia trusted publisher workflow]

Loading

_{Reviews (1): Last reviewed commit: "chore(main): release 0.5.3" | Re-trigger Greptile}