Repository navigation
chore: prepare 0.15.2 release - #253
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: aa26c64425
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Unreleased | ||
|
|
||
| ## 0.15.2 - 2026-10-16 |
There was a problem hiding this comment.
Once this section makes 0.15.2 the current release candidate, the README still instructs maintainers to dispatch the required dry run with version=0.15.1 (README.md:91), despite immediately saying to use the current version. Following that command validates artifacts carrying the previous version rather than the 0.15.2 artifacts that will be published, so update the example as part of this release preparation.
Useful? React with 👍 / 👎.
1 participant
Prepare Gitcrawl 0.15.2 with reliable local database initialization inside Git worktrees, refreshed dependencies, and the explicit release dry run.
This is a patch release: the product changes fix existing behavior and update dependencies; the new dry-run input is maintainer release tooling. All three Unreleased bullets and all historical bullets are preserved verbatim, including contributor credit. The empty Unreleased section remains ready for the next changes.
Validation: release-script checks passed; independent Codex autoreview passed at P0–P3; exact-head CI is required before merging. Publication will use the documented unified Actions pipeline, with a successful dry run first.