ci: auto-create GitHub Release with notes on every version tag#3
Merged
Conversation
kool7
added a commit
that referenced
this pull request
May 4, 2026
Incorporates all changes cleanly on top of main (after PR #2 relative-paths fix and PR #3 CI release automation): - Parse arc table for branch-coverage .coverage files (coverage.py branch=true) - inferMissingLines tracks bracket depth — no false reds on __all__, multi-line calls - Pytest auto-run via child_process.spawn — no ^C corruption from Python extension - Debounced file-watcher reloads, mutex on handleNoCoverage prompt - Consistent filtered % across status bar, tree Overall, and dashboard ring - displayPath (workspace-relative) preserved from PR #2 in both dashboard and tree - Empty-file filter from PR #2 combined with test-file filter (excludeTestFiles) - Dashboard tab ThemeIcon, header inline SVG — both themes correct - Coverage tree back in Explorer panel, Summary clickable to open dashboard - Removed info-message toast on every reload
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.
What
After publishing to the VS Code Marketplace, also create a proper GitHub Release with auto-generated changelog notes.
Why
Currently only a git tag is created on each version. Open source convention is to have a Release page with changelogs — makes the repo look professional and gives users a history to read.
What changed
Added
softprops/action-gh-release@v2step topublish.yml. It runs aftervsce publishand creates a GitHub Release automatically with notes generated from commits since the previous tag.From
v0.0.6onwards every release will appear atgithub.com/kool7/coverage-visualizer/releaseswith a full changelog.