release-changelog
Skill1.1k starsChanged 6 days agoMITView on GitHub
Prepare a Hail release — bump the patch version and curate the query and batch changelogs from commits since the last release tag
20 other projects use a version of this.
Trending
Less talk lately.about the whole repository
Most recently taken up by
- pipeshub-ai/pipeshub-aitheir own version, first seen Nov 13, 2026
- AndersonAndrad/skillstheir own version, first seen Nov 8, 2026
- withpiper/pipekittheir own version, first seen Nov 8, 2026
- tanpenggood/skillstheir own version, first seen Nov 1, 2026
- etejedaw/workflow-skillstheir own version, first seen Oct 25, 2026
- Hans010101/bitworldtheir own version, first seen Oct 20, 2026
Who's talking about hail-is/hail
- ipython/ipython“In ipython 8.18 (but not ipython 8.16), the current event loop is overwritten in each cell”GitHub · Jan 17, 2024 · 7 reactions
- @stephenturner.us“The Scalable Variant Call Representation: Enabling Genetic Analysis Beyond One Million Genomes …”Bluesky · Jan 12, 2024 · 7 likes
- has2k1/plotnine“Request: re-license under MIT?”GitHub · Dec 6, 2021 · 3 reactions
- Stack Overflow“Get relative path from inside a scala library (while developing that library)”Stack Overflow · Nov 27, 2018 · 3 votes
- d12frosted/homebrew-emacs-plus“Fix linking how-to in formula caveats”GitHub · Dec 21, 2023 · 2 reactions
The biggest 5 of 54 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 54
Talked about on GitHub, Stack Overflow, Hacker News and Bluesky (54 times).
On GitHub · 50
- Jan 17, 2024In ipython 8.18 (but not ipython 8.16), the current event loop is overwritten in each cell — ipython/ipython7 reactions · 2 comments
- Dec 6, 2021Request: re-license under MIT? — has2k1/plotnine3 reactions · 1 comment
- Dec 21, 2023Fix linking how-to in formula caveats — d12frosted/homebrew-emacs-plus2 reactions
- Dec 14, 2023Incorrect lint in 0.1.8? RUF006 Store a reference to the return value of `asyncio.create_task` — astral-sh/ruff2 reactions · 9 comments
- Nov 4, 2026New hail-is/hail version available: 0.2.140 — TheBoutrosLab/docker-Hail1 reaction
45 more on GitHub
- Aug 20, 2026New hail-is/hail version available: 0.2.139 — TheBoutrosLab/docker-Hail1 reaction
- Feb 7, 2021Hail developer set-up — populationgenomics/team-docs1 reaction
- Aug 4, 2026Bump the pip group across 1 directory with 5 updates — broadinstitute/variant-curation-portal0 reactions
- Jun 24, 2026Update hadoop to hailtop after hail's hadoop deprecation — broadinstitute/gnomad_methods0 reactions · 2 comments
- Jun 16, 2026[skill-suggestion] hail: scalable genomic analysis and GWAS engine (Broad Institute) — stanfish06/skillquarium0 reactions
- Sep 11, 2025[explore] Variant store: Hail — tidywf/nemo0 reactions
- Jul 25, 2025Add LEN to compute_stats_per_ref_site after hail updates — broadinstitute/gnomad_methods0 reactions
- Mar 14, 2025Temporarily revert username validation, as new rule disallows dashes — populationgenomics/hail0 reactions
- Jan 10, 2025Refine combiner usage — populationgenomics/production-pipelines0 reactions · 1 comment
- Dec 16, 2024fix: remove obsolete Hortonworks repositories — h2oai/h2o-30 reactions · 6 comments
- Dec 15, 2024Cherry-pick upstream fix: Set StreamReadConstraints maxStringLength as early as possible — populationgenomics/hail0 reactions
- Sep 20, 2024Bump the pip group with 4 updates — broadinstitute/variant-curation-portal0 reactions · 2 comments
- Jul 15, 2024chore(deps): bump the pip group across 2 directories with 15 updates — broadinstitute/gnomad-browser0 reactions · 4 comments
- Jul 5, 2024chore(deps): bump the pip group across 2 directories with 14 updates — broadinstitute/gnomad-browser0 reactions · 1 comment
- Jun 17, 2024chore(deps): bump the pip group across 3 directories with 14 updates — broadinstitute/gnomad-browser0 reactions · 1 comment
- Jun 11, 2024chore(deps): bump the pip group across 3 directories with 15 updates — broadinstitute/gnomad-browser0 reactions · 2 comments
- Jun 11, 2024chore(deps): bump the pip group across 3 directories with 14 updates — broadinstitute/gnomad-browser0 reactions · 1 comment
- Jun 10, 2024chore(deps): bump the pip group across 3 directories with 13 updates — broadinstitute/gnomad-browser0 reactions · 1 comment
- Jun 6, 2024chore(deps): bump the pip group in /data-pipeline with 12 updates — broadinstitute/gnomad-browser0 reactions · 1 comment
- May 14, 2024Fix syntax — broadinstitute/seqr-loading-pipelines0 reactions
- May 1, 2024Local_to_global: local alleles not strictly increasing: [0,2,1] — iris-garden/test-process0 reactions
- May 1, 2024Where to find data for practicing using Hail — iris-garden/test-process0 reactions
- Apr 30, 2024De novo confidence queries — iris-garden/test-process0 reactions
- Apr 30, 2024DNANexus: hail installation on custom spark cluster — iris-garden/test-process0 reactions
- Apr 30, 2024Hail architecture or design philosophy — iris-garden/test-process0 reactions
- Apr 30, 2024Assertion Error during entries().show() — iris-garden/test-process0 reactions
- Apr 30, 2024Dataproc connect should support --project command line option — iris-garden/test-process0 reactions
- Apr 30, 2024CollectionExpression join — iris-garden/test-process0 reactions
- Apr 30, 2024Use agg.linreg for GWAS — iris-garden/test-process0 reactions
- Apr 30, 2024Limit memory usage — iris-garden/test-process0 reactions
- Apr 30, 2024ArrayIndexOutOfBoundsException error in hail 0.2.40 — iris-garden/test-process0 reactions
- Apr 30, 2024Import_bgen 16 bits error — iris-garden/test-process0 reactions
- Apr 30, 2024VCF4.1, is.hail.utils.HailException: array index out of bounds — iris-garden/test-process0 reactions
- Apr 30, 2024How to get the ration transition-transversion on all dataset? — iris-garden/test-process0 reactions
- Apr 30, 2024GQ set to NA when PL is NA after split_multi_hts — iris-garden/test-process0 reactions
- Apr 30, 2024Download for tutorial notebooks — iris-garden/test-process0 reactions
- Apr 30, 2024Typo in impute_sex() description — iris-garden/test-process0 reactions
- Apr 30, 2024Hail V01 to V02 missing genotypes? — iris-garden/test-process0 reactions
- Apr 30, 2024Import_table on gs with wildcard — iris-garden/test-process0 reactions
- Apr 30, 2024Hail 0.2.10 patch notes — iris-garden/test-process0 reactions
- Apr 30, 2024Interval.parse in v0.2 — iris-garden/test-process0 reactions
- Apr 30, 2024Hail 0.2.6 patch notes — iris-garden/test-process0 reactions
- Apr 30, 2024Hail 0.2.5 patch notes — iris-garden/test-process0 reactions
- Apr 30, 2024Chained logistic regression — iris-garden/test-process0 reactions
- Apr 30, 2024[Breaking change] partition keys removed from python interface — iris-garden/test-process0 reactions
On Stack Overflow · 2
On Hacker News · 1
- Aug 28, 2020Hail.is: open-source library for exploring genomic data1 point
On Bluesky · 1
- Jan 12, 2024The Scalable Variant Call Representation: Enabling Genetic Analysis Beyond One Million Genomes www.biorxiv.org/content/10.1... 🧬🖥️… — @stephenturner.us7 likes and reposts
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- paperclipai/paperclip★ 114ksame name
- umijs/qiankun★ 17ksame name
- newton-physics/newton★ 6ksame name
- pipeshub-ai/pipeshub-ai★ 4.1ksame name
- VoidenHQ/voiden★ 1.8ksame name
- Harry-kp/vortix★ 779same name
- mikeyobrien/rho★ 372same name
- Kong/developer.konghq.com★ 28same name
- ancilis/bedlam★ 15same name
- yjhmelody/nanobot-rs★ 15same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- hail/AGENTS.mdAGENTS.md
- hail/CLAUDE.mdCLAUDE.md
- flamegraphSkill
- hail-batch-devSkill
- hail-batchSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run the helper script from the hail/ directory (it uses relative paths):
- Very specific: line 44
Only reach for gh pr view when you need post-merge context: review comments, linked issues, or a description edited after merge.
- Distinctive: line 49
Keep entries that affect users.
- Distinctive: line 69
Verify every bug-fix entry against the previous release: Only bugs that existed in a released version belong in the changelog.
- Distinctive: line 78
If the culprit can't be pinned down, keep the entry and flag it in the summary.
- Distinctive: line 80
When a commit's noteworthiness or user-visible symptom is unclear from its message, read the PR body (already in the commit body), the …
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are preparing the changelog portion of a quarterly Hail release. The deliverable is a version bump plus curated, user-facing changelog entries in two files. A human reviews the result, so flag any borderline noteworthiness calls in your final summary rather than silently dropping them.
Steps
1. Bump the patch version
Two places, which must agree (skip if already done — check git diff):
hail/Makefile:HAIL_PATCH_VERSION := <n+1>hail/build.mill:val hailPatchVersion = "<n+1>"
The previous version is the latest git tag (e.g. 0.2.138): git describe --tags $(git rev-list
--tags --max-count=1).
2. Generate raw changelog entries
Run the helper script from the hail/ directory (it uses relative paths):
cd hail && scripts/update-changelogIt prepends a new version section with one line per commit to both changelogs, filtered by the
[tag] in each commit subject (query-ish tags → python/hail/docs/change_log.md, service-ish
tags → python/hailtop/batch/docs/change_log.rst). Skip this step if the raw entries are already
present.
3. Gather context on each commit
PRs are squash-merged, so the commit body contains the full PR description — do NOT fetch PR metadata from GitHub for this. One local command gives everything:
git log --format='%h %s%n%b%n---' <prev-tag>..HEADOnly reach for gh pr view when you need post-merge context: review comments, linked issues, or a
description edited after merge.
4. Curate
Keep entries that affect users; drop internal noise; reword keepers into each file's style.
Noteworthy:
- New features, new API surface (functions, parameters, CLI commands, endpoints)
- Bug fixes users could have hit, including performance regressions
- Performance improvements users will notice
- Deprecations and removals (including parameters becoming no-ops)
- File-format or on-disk layout changes — always state the compatibility direction explicitly (typically: new version reads old files, old versions cannot read new files)
- Major dependency changes: Python, Spark, Scala, Java versions
- Notable infrastructure changes users see in behavior or billing (e.g. worker machine family)
Not noteworthy:
- Internal refactors (compiler internals, no-sharing invariants, code organisation)
- Build/CI/test tooling changes
- Routine dependency bumps: pip/npm packages, Ubuntu base images, build tools
- Logging tweaks and docs-only nits
- Bugs both introduced and fixed since the previous tag — no released version ever had them
- Likewise, any other feature or change both introduced and rolled back since the previous tag
Verify every bug-fix entry against the previous release. Only bugs that existed in a released
version belong in the changelog. For each fix, find the commit that introduced the bug (the PR
body often names the culprit PR; otherwise use the diff, git log -S, or git log --follow on
the touched code) and check whether it shipped:
git merge-base --is-ancestor <introducing-commit> <prev-tag> && echo "shipped — keep" || echo "drop"If the culprit can't be pinned down, keep the entry and flag it in the summary.
When a commit's noteworthiness or user-visible symptom is unclear from its message, read the PR body (already in the commit body), the linked issue, or the diff. If still unsure, keep your best judgment in the file and flag it in the summary.
5. Reword to match each file's style
Study the previous version's section in each file first; match it. Use American English spellings (behavior, materialize, randomization — not behaviour, materialise, randomisation).
Query changelog (hail/python/hail/docs/change_log.md, Markdown):
## Version 0.2.NNN
Released YYYY-MM-DD
### New Features
- (hail#15445) Table and matrix table index files are now written as a single file ...
### Bug Fixes
- (hail#15374) Fix a bug where `sparse_split_multi` crashed on haploid genotypes ...
### Deprecations
- (hail#15589) The `stage_locally` parameter of write methods no longer has any effect ...- Three
###subsections: New Features, Bug Fixes, Deprecations (omit an empty subsection). - Perf improvements go under New Features; perf regression fixes under Bug Fixes ("Fix a performance regression where ...").
- Bug fixes start "Fix a bug where ..." and describe the user-visible symptom, naming the Python
API (
hl.foo, backtick-quoted), not compiler internals. - The script leaves an empty section skeleton and trailing whitespace on headings — clean both up.
Batch changelog (hail/python/hailtop/batch/docs/change_log.rst, RST):
**Version 0.2.NNN**
- (`#15200 <https://github.com/hail-is/hail/pull/15200>`__) All services now use ...- Flat list, no subsections. Order: major changes first, then features, then fixes.
- Double backticks for code (RST):
hailctl batch jobs. - Audience includes end users of hailtop.batch/hailctl AND operators of Hail deployments; admin UI button-level fixes are usually too minor unless they shipped broken in a prior release.
- Several PRs delivering one change (e.g. the same feature split per-service) may share one entry with all PR links.
6. Summarise for review
End with: what you kept per file, what you dropped and why (grouped, not exhaustive), and the specific judgment calls the releaser should double-check.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

