release: bump yertle to 0.2.0

[albertcmiller1]

Version

0.2.0 — MINOR, per PACKAGING.md's rule "New endpoints or new SDK functions → MINOR bump." yertle auth status is new; nothing was deleted or renamed from the public facade, so it isn't MAJOR.

0.1.0 is already published and PyPI never allows reusing a version, so this bump is a hard prerequisite for the release.

What 0.2.0 ships

PR
#12	yertle auth status — per-key credential provenance
#13	source-checkout flag in yertle version; version read from distribution metadata
#14	yertle-client 0.2.0, dependency floor raised to >=0.2.0
#15	credentials written 0600, merged not clobbered, written atomically

Also re-locks uv.lock

The 0.1.0 bump in 83116c3 changed pyproject.toml without re-locking, so uv.lock carried a stale version = "0.0.1" until an unrelated uv sync picked it up incidentally (noted in #12). Bumping and locking in the same commit here so that can't recur.

Testing

make check green (81 tests). Beyond that, the artifact itself:

$ uv build
Successfully built dist/yertle-0.2.0.tar.gz
Successfully built dist/yertle-0.2.0-py3-none-any.whl

# installed into a clean venv:
$ yertle version
0.2.0                      # bare — no "editable" suffix, as expected for a wheel
$ yertle auth status       # authenticates against a live backend

That last check exercises both halves of #13: the version is metadata-driven (so this PR bumps exactly one file, not two), and the editable-detection correctly reports not editable for a real install.

Release notes for whoever tags this

Two user-visible behaviour changes worth calling out:

• yertle version reports 0.2.0. The published 0.1.0 wheel reported 0.0.1 due to the hardcoded-__version__ drift feat(cli): flag source checkouts in yertle version #13 fixed, so this is the first release where the reported version matches the package.
• Existing config files are silently tightened to 0600 on the user's next yertle login (fix(auth): write credentials 0600, merge instead of clobber, write atomically #15). Intended repair, but better announced than discovered.

Follow-up needed in the yertle repo

PACKAGING.md's version-bump playbook step 2 says to "also bump __version__ in src/yertle/__init__.py". That hardcoded copy no longer exists — #13 replaced it with importlib.metadata, which is what deployments.txt already documents. Following PACKAGING.md literally would re-introduce the drift it warns about. Separate PR, different repo.

🤖 Generated with Claude Code