growth: PyPI nanoodle is 0.5.0, and the sample run now reaches video - #377
Open
mikkel wants to merge 1 commit into
Open
growth: PyPI nanoodle is 0.5.0, and the sample run now reaches video#377mikkel wants to merge 1 commit into
mikkel wants to merge 1 commit into
Conversation
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nanoodle | 0f97414 | Commit Preview URL Branch Preview URL |
Aug 04 2026, 04:44 AM |
I published nanoodle 0.5.0 to PyPI today, so the launch drafts and the re-check block stated a stale version. check-launch-facts passed on the stale number, because it reads the committed re-check block instead of live PyPI. Re-verified all 3 published versions live on 2026-07-29: npm nanoodle 0.8.0, npm nanoodle-mcp 0.4.0, PyPI nanoodle 0.5.0. Also records what the 5 pull requests of 2026-07-29 changed after the Jul 28 fact-check pass. None makes a claim in the drafts false. One is worth adding to the copy before posting: a signed-out visitor now reaches a video result in the sample run, with no account and no key. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mikkel
force-pushed
the
growth/pypi-0-5-0
branch
from
August 4, 2026 04:43
643853c to
0f97414
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
I published
nanoodle0.5.0 to PyPI today (release: https://github.com/nanoodlecom/nanoodle-py/releases/tag/v0.5.0). The launch drafts and the checklist's re-check block still said 0.4.0.scripts/check-launch-facts.mjspassed on the stale number. That is by design and worth knowing: the guard reads the version from the committed re-check block ingrowth/launch-checklist.md, not from live npm or PyPI. It keeps the 6 launch files agreeing with each other and with that block. It cannot notice that the block itself went stale.What changed
nanoodle0.8.0, npmnanoodle-mcp0.4.0, PyPInanoodle0.5.0.growth/launch-checklist.mdandgrowth/product-hunt-draft.md.One thing to read before posting
nanoodle#376merged today. A signed-out visitor now reaches a video result in the sample run, with no account and no key. The drafts were written when the sample covered text and images only, so the hooks undersell it. The showcase is also linked from the product now, which the Product Hunt draft's demo section could use.I did not rewrite the launch copy. That is a voice decision, and only Mikkel posts.
Verification
node scripts/check-launch-facts.mjs→ ok, 6 launch files, 10 examples, versions npm nanoodle 0.8.0, npm nanoodle-mcp 0.4.0, PyPI nanoodle 0.5.0.scripts/check-*.mjsguards pass, 0 fail..githooks/pre-commit, no--no-verify.lora-models.jsonrestored after the guard loop and kept out of the commit.🤖 Generated with Claude Code