Prepare v1.1.0: bump version + fix stale troubleshooting invocations#9
Merged
Conversation
Version bump: - pyproject.toml: 1.0.0 -> 1.1.0 - src/substack_link_checker/__init__.py: __version__ -> 1.1.0 - CHANGELOG.md: rename [Unreleased] -> [1.1.0] - 2026-05-19, add a fresh empty [Unreleased] section above it Troubleshooting fix: - README.md Troubleshooting section's code blocks still used the pre-refactor `python substack_link_checker.py ...` / `python fetch_archive_urls.py ...` form because PR #4 was based on the audit branch before B3's CLI rewrite landed. Updated to the current `substack-link-checker check ...` and `substack-link-checker fetch-archive ...` invocations so a reader following the troubleshooting steps doesn't hit "command not found" on the main entry point. Once this lands, push tag v1.1.0 to trigger the release workflow (which builds the wheel/sdist and attaches them to the GitHub Release).
The CI test job has been running `python substack_link_checker.py --help` as a post-install smoke test since PR #1. B3 (PR #3) deleted that file when refactoring the codebase into the src-layout package, but didn't update this step. CI has been failing on every PR since B3 merged. Replace with two invocations against the installed console script: - `substack-link-checker --help` (top-level dispatcher) - `substack-link-checker check --help` (check subcommand) This is also why the actions/checkout Dependabot PR (#7) was reported as failing — same root cause, not the action bump itself.
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
2 participants
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
Prepares the repo for a
v1.1.0release covering all the post-v1.0.0 audit work (PRs #1, #2, #3, #4, #5).Version bump:
pyproject.tomlandsrc/substack_link_checker/__init__.py:1.0.0→1.1.0CHANGELOG.md: renames[Unreleased]→[1.1.0] - 2026-05-19, adds a fresh empty[Unreleased]section above itTroubleshooting fix (carryover from #4):
python substack_link_checker.py .../python fetch_archive_urls.py ...because PR B9: add Troubleshooting section to README #4 was based on the pre-B3 audit branch. Updated tosubstack-link-checker check ...andsubstack-link-checker fetch-archive ...so the section is internally consistent with the rest of the README.What you do after merge
Push the tag — that's it. The release workflow (
/.github/workflows/release.ymlfrom PR #2) takes care of building wheel+sdist and attaching them to a GitHub Release.Test plan
pytest→ 38 passing locallysubstack-link-checker --version→substack-link-checker 1.1.0pyproject.tomlis now1.1.0)v1.1.0Release on GitHub hassubstack_broken_link_checker-1.1.0-py3-none-any.whland.tar.gzattachedGenerated by Claude Code