chore(main): release 0.19.0

[mlorentedev]

🤖 I have created a release beep boop

0.19.0 (2026-06-25)

Features

• secrets: resolve nan-* scripts' NAN_API_KEY via dotf secrets show (#588) (3245be5)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features
  • Added support for resolving NAN_API_KEY for nan-* scripts through dotf secrets show.
• Chores
  • Updated the project to version v0.19.0.
  • Added the new v0.19.0 changelog entry.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 49ec52d7-f072-48dd-ba5c-4d3667758801

📥 Commits

Reviewing files that changed from the base of the PR and between 3245be5 and 59fd188.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• versions.conf

---

📝 Walkthrough

Walkthrough

Bumped the project release version to 0.19.0 and added the corresponding changelog entry describing the new secrets resolution behavior.

Changes

Release metadata update

Layer / File(s)	Summary
Version bump and changelog entry .release-please-manifest.json, versions.conf, CHANGELOG.md	The root release version and DOTF_VERSION were updated from 0.18.0 to 0.19.0, and the changelog added the v0.19.0 features entry for resolving NAN_API_KEY via dotf secrets show.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• mlorentedev/dotfiles#412: Updates the same DOTF_VERSION field in versions.conf.
• mlorentedev/dotfiles#421: Also coordinates .release-please-manifest.json, versions.conf, and CHANGELOG.md release-version updates.
• mlorentedev/dotfiles#582: Adds an earlier secrets release note path that this changelog entry continues.

Poem

I nibbled the carrot of versioning bright,
Then hopped to 0.19.0 in moonlit light.
My whiskers read changelogs, tidy and neat,
While secrets and scripts did a little dance-sweet.
🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes release notes, but it does not follow the required template sections like Summary, SDD checklist, or Test plan.	Rewrite the PR body using the repository template and fill in Summary, SDD checklist, optional skip rationale, and Test plan sections.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies this as a release for version 0.19.0, matching the main change in the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

_{Comment @coderabbitai help to get the list of available commands.}

[mlorentedev]

🤖 Created releases:

• v0.19.0

🌻