chore: bump to v0.5.0

[jan-kubica]

Minor version bump for tsdown migration.

---

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🚩 Version jump from 0.2.0 to 0.5.0 skips intermediate minor versions

The version jumps from 0.2.0 directly to 0.5.0, skipping 0.3.x and 0.4.x. Looking at the git history, there are many feature PRs between the last version and this bump (#64–#72), including new generate() functionality, strict TypeScript fixes, and a build tool migration. While semver doesn't require sequential minor versions, this jump is unusual and may indicate that intermediate releases were planned but never tagged, or that a different versioning strategy is being adopted. Worth confirming this is intentional.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[greptile-apps]

Greptile Summary

This PR bumps the package version from 0.2.0 to 0.5.0 in package.json, intended to formally publish the accumulated changes since the last release — most notably the migration from tsup to tsdown as the build tool.

Key observations:

• The version jumps 3 minor versions (0.2.0 → 0.5.0), which is intentional given the many unreleased features added since 0.2.0 (new validators, generate(), find(), TypeScript strict fixes, etc.).
• CHANGELOG.md follows the "Keep a Changelog" format but has not been updated since v0.1.0 — neither v0.2.0 nor v0.5.0 have changelog entries despite meaningful changes.
• No other files are changed; the build tooling (tsdown) and all exports remain as established in the preceding commit.

Confidence Score: 4/5

• Safe to merge — the only change is a version number in package.json with no functional impact on source code.
• The change is a single-line version bump with no risk of runtime breakage. The minor concern is that the CHANGELOG is not updated, which is a process/documentation issue rather than a code correctness one.
• No files require special attention beyond the CHANGELOG.md omission noted in the inline comment.

Important Files Changed

Filename	Overview
package.json	Version bumped from 0.2.0 to 0.5.0; the only change in this PR. The jump of 3 minor versions is intentional to account for unreleased feature additions, but the CHANGELOG.md was not updated.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["v0.1.0 – Initial release"] --> B["v0.2.0 – Compiled dist output added"]
    B --> C["Features & fixes merged to main\n(generate, find, new validators,\nTypeScript strict, tsdown migration)"]
    C --> D["This PR: package.json version → v0.5.0"]
    D --> E["npm publish @stll/stdnum@0.5.0"]
    style D fill:#f0f4ff,stroke:#4a6cf7
    style E fill:#e6ffe6,stroke:#2e7d32

Loading

_{Reviews (1): Last reviewed commit: "chore: bump to v0.5.0" | Re-trigger Greptile}

[greptile-apps]

CHANGELOG not updated for v0.5.0

The project's CHANGELOG.md explicitly states it follows the Keep a Changelog format and adheres to Semantic Versioning, but it has not been updated to include an entry for v0.5.0 (or the earlier v0.2.0 either). The git history since v0.2.0 includes a number of meaningful changes — new validators, new capabilities like generate() and find(), TypeScript strict mode fixes, and the tsdown migration — that would be worth documenting for downstream consumers.

Consider adding a ## [0.5.0] section to CHANGELOG.md summarising the notable changes since v0.1.0 before publishing.