Release anouncement for 0.0.62 - #428
Merged
Merged
Conversation
Contributor
Reviewer's GuideThis PR updates the docs tooling command, adds a comprehensive release announcement blog post for Lets 0.0.63, and introduces a research document describing patterns for writing release announcements (specifically for v0.0.62), alongside locking docs dependencies via package-lock updates. Flow diagram for updated docs command in lets.yamlflowchart LR
dev[Developer] --> lets_docs[lets docs]
lets_docs --> npm_install[npm install]
npm_install --> npm_start[npm start]
npm_start --> docs_server[Docs dev server running]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Hey - I've found 2 issues, and left some high level feedback:
- There’s a version mismatch between the PR title (0.0.62) and the new blog post (0.0.63); align the naming and release references so it’s clear which version this announcement is for.
- Renaming
run-docstodocsand addingnpm install && npm startwill reinstall dependencies on every run; consider usingnpm ciduring a dedicated install step or a separate command to avoid redundant installs and speed up docs development.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- There’s a version mismatch between the PR title (0.0.62) and the new blog post (0.0.63); align the naming and release references so it’s clear which version this announcement is for.
- Renaming `run-docs` to `docs` and adding `npm install && npm start` will reinstall dependencies on every run; consider using `npm ci` during a dedicated install step or a separate command to avoid redundant installs and speed up docs development.
## Individual Comments
### Comment 1
<location path="docs/blog/2026-08-02-lets-0.0.63.md" line_range="44" />
<code_context>
+
+If none is available, the installer creates `$HOME/.local/bin`, places the symlink there, and asks to add that directory to your shell profile.
+
+If you want to install lets on CI or in Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts.
+
+`lets self upgrade` follows the symlink and replaces the managed target. It refuses common system-managed locations and redirects Homebrew users to the correct package-manager command.
</code_context>
<issue_to_address>
**nitpick (typo):** Clarify wording around CI/Docker installation
Please rephrase to: "If you want to install Lets on CI or in a Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts." This fixes the missing article and aligns the product name capitalization.
```suggestion
If you want to install Lets on CI or in a Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts.
```
</issue_to_address>
### Comment 2
<location path="docs/blog/2026-08-02-lets-0.0.63.md" line_range="313-315" />
<code_context>
+
+## Personal Lets settings
+
+Lets now allows to configure personal preferences:
+
+```text
</code_context>
<issue_to_address>
**suggestion (typo):** Fix grammatical issue in "allows to configure"
Consider rephrasing to a grammatical alternative such as “Lets now lets you configure personal preferences:” or “Lets now allows you to configure personal preferences:”.
```suggestion
## Personal Lets settings
Lets now lets you configure personal preferences:
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
|
||
| If none is available, the installer creates `$HOME/.local/bin`, places the symlink there, and asks to add that directory to your shell profile. | ||
|
|
||
| If you want to install lets on CI or in Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts. |
Contributor
There was a problem hiding this comment.
nitpick (typo): Clarify wording around CI/Docker installation
Please rephrase to: "If you want to install Lets on CI or in a Dockerfile, use LETS_INSTALL_NO_PROMPT=1 to suppress profile updating prompts." This fixes the missing article and aligns the product name capitalization.
Suggested change
| If you want to install lets on CI or in Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts. | |
| If you want to install Lets on CI or in a Dockerfile, use `LETS_INSTALL_NO_PROMPT=1` to suppress profile updating prompts. |
Comment on lines
+313
to
+315
| ## Personal Lets settings | ||
|
|
||
| Lets now allows to configure personal preferences: |
Contributor
There was a problem hiding this comment.
suggestion (typo): Fix grammatical issue in "allows to configure"
Consider rephrasing to a grammatical alternative such as “Lets now lets you configure personal preferences:” or “Lets now allows you to configure personal preferences:”.
Suggested change
| ## Personal Lets settings | |
| Lets now allows to configure personal preferences: | |
| ## Personal Lets settings | |
| Lets now lets you configure personal preferences: |
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.
Summary by Sourcery
Add documentation content for the Lets 0.0.63 release, including a release announcement and supporting editorial research, and update the docs command in the task runner configuration.
Enhancements:
docs.Documentation: