Releases: X-PG13/callchain
Releases · X-PG13/callchain
v0.2.0a2
Highlights
- Fixes the release pipeline by vendoring the
click-srccorpus snapshot into the repository. - Makes
Corpus Baseline, release validation, and GitHub-hosted release automation independent of a localdownloaded_repos/checkout. - Cuts a clean follow-up prerelease after the failed
0.2.0a1workflow run.
Changelog
Changed
- Vendored the
click-srccorpus snapshot intotest_repos/vendored/clickso corpus baseline, release validation, and GitHub-hosted workflows no longer depend on a localdownloaded_repos/checkout.
Release Corpus Audit (v0.2.0a2)
- Status:
official_baseline_only - Recommendation: Official baseline is the only release-time corpus reference.
- Evidence: release workflow run, corpus state artifact, distribution artifact bundle
- Note: No refresh candidate exists; the official baseline is the current release reference.
Corpus release state
Corpus Release State
- Status:
official_baseline_only - Pending refresh allowed:
false - Recommendation: Official baseline is the only release-time corpus reference.
| Record | Run | Created | Branch | Commit | Event | Artifact |
|---|---|---|---|---|---|---|
| Official baseline | run 24116452430 |
2026-04-08T03:42:14Z |
main |
94b5861 |
workflow_dispatch |
corpus-baseline-24116452430 (active) |
| Latest branch compare | none |
n/a |
n/a |
n/a |
n/a |
none |
| Refresh candidate | none |
n/a |
n/a |
n/a |
n/a |
none |
No refresh candidate exists; the official baseline is the current release reference.
v0.2.0a1 (superseded by v0.2.0a2)
Warning
This prerelease has been superseded by v0.2.0a2.
Use v0.2.0a2 instead: https://github.com/X-PG13/callchain/releases/tag/v0.2.0a2
v0.2.0a1 is kept only as a historical record of the first prerelease attempt.
Its release workflow did not complete successfully, and it should not be used for evaluation or installation.
Historical notes
This release originally introduced the repository-grade automation, corpus tooling, install-smoke workflow, and richer example projects listed below. It has since been replaced by v0.2.0a2, which includes the corrected corpus baseline setup required for GitHub-hosted release validation.
Original changelog
Added
- Dependency review, release drafter, and PR autolabeler workflows for tighter repository automation
- Repository label taxonomy with sync workflow and stale issue/PR triage automation
- CodeQL scanning, scheduled dependency auditing, and CycloneDX SBOM export workflow automation
- Citation metadata, support guidance, and typed-package markers for downstream consumers
- Local corpus regression and benchmark tooling for smoke repos and a vendored real-world sample repository
- Corpus report comparison tooling for reviewing structural deltas and timing regressions between stored snapshots
- Corpus sample provenance registry and validation tooling for vendored source metadata
- Corpus source sync tooling to refresh vendored sample refs and checksums from local contents
- Vendored corpus source refresh tooling for git-backed sample upgrades with registry sync
- Vendored corpus archive verification tooling with recorded upstream archive URLs and checksums
- Vendored corpus materialization tooling for archive-backed snapshot reconstruction and one-step maintainer updates
- Manual GitHub Actions corpus-maintenance workflow for vendored source verify/materialize snapshot review
- Scheduled/manual GitHub Actions corpus-baseline workflow plus local baseline capture target
- GitHub Actions corpus-baseline-compare workflow for consuming the latest official baseline artifact on branch checks
- GitHub Actions corpus-baseline-refresh workflow for post-merge baseline candidate capture after drift-approved PRs
- Install-smoke tooling for validating built artifacts against a packaged example repository
- TestPyPI rehearsal and post-release smoke workflows for registry-level package verification
- Real-world example projects for Python service, TypeScript dashboard, and C++ library walkthroughs
Changed
- New bug reports and feature requests now start with a
needs-triagelabel for consistent maintainer intake - Developer tooling now includes local vulnerability audit and SBOM generation targets, plus stricter pre-commit hygiene hooks
- Release tooling now keeps
CITATION.cffaligned with package version and release date metadata - CI now runs a dedicated corpus regression job, while timing benchmarks stay as local advisory tooling
- CI now runs a fresh-venv install-smoke matrix against the built distribution and packaged example repo
- Install-smoke tooling now supports package-index mode for TestPyPI/PyPI verification
- README and examples documentation now follow task-oriented first-user workflows instead of a single smoke-only path
- Corpus maintenance guidance now includes snapshot capture and explicit before/after report comparison
- Corpus maintenance now records upstream, version, and license metadata for each sample repository
- Corpus maintenance now records and can refresh vendored sample commit refs and content checksums
- Corpus report comparison now supports summary-only drift gates for stable parser/resolver snapshot review
- Corpus baseline compare automation now emits Markdown review notes and sticky PR comments alongside JSON artifacts
- Corpus baseline compare automation now cross-checks review hints against the PR changed-file list
- Corpus baseline compare automation now derives CODEOWNERS-backed owner hints for touched drift surfaces when repository ownership rules are configured
- Corpus baseline compare automation now derives a priority-sorted owner focus for reviewer routing from CODEOWNERS-backed drift matches
- Corpus baseline compare automation now derives reviewer candidates and a review-request dry-run from CODEOWNERS-backed routing data without issuing actual reviewer requests
- Release corpus audit rendering now trims compare evidence into a severity-sorted focus view for the most important drift cases
- Release corpus audit summaries now classify compare drift into parser, resolver, parse-health, and non-structural buckets
- Release corpus audit summaries now include finer discovery, symbol-extraction, call-resolution, and chain-enumeration attribution hints
- Release corpus audit summaries now derive likely implementation modules to review from drift attribution signals
- Release corpus audit summaries now retain compare-time owner hints so release reviewers can route drift evidence to likely maintainers
- Release corpus audit summaries now retain compare-time owner focus so release reviewers can see the highest-priority likely maintainers first
- Release corpus audit summaries now retain compare-time reviewer candidates and review-request dry-run output for release review routing
- Release corpus audit summaries now retain compare changed-file context and show overlap between branch edits and likely review modules
- Release corpus audit summaries now priority-sort changed-file overlap so core module hits surface first
- Corpus baseline compare automation now supports explicit maintainer drift waivers via PR label or manual workflow input
- Release automation now publishes a rendered corpus baseline state summary and raw state artifact alongside release validation, with direct run/artifact links, branch compare evidence, compare-report excerpts, review context, and an auditable GitHub Release body section