chore: release v0.5.0 with T-SQL rules#24
Merged
Pawansingh3889 merged 2 commits intomainfrom Apr 20, 2026
Merged
Conversation
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.
Release prep for v0.5.0, bundling the T-SQL rules merged in #23.
What
pyproject.tomlversion 0.4.1 → 0.5.0.README.mdhero line and rules table refreshed: 29 rules (25 SQL +4 Python), new T-SQL section added with T001-T004.
README.mdpre-commit hook example bumped torev: v0.5.0..pre-commit-config.yamlself-reference bumped from v0.4.0 to v0.5.0,closing the drift that pr-sop's
precommit_rev_matches_taghas beenwarning on since v0.4.1.
CHANGELOG.md[Unreleased] section rotated to [0.5.0] with today'sdate.
Sequencing
pr-sop's
precommit_rev_matches_tagcheck compares self-rev pins tothe latest git tag. On this PR the refs say v0.5.0 but the latest tag
is still v0.4.1, so the check will warn (severity warning in
.prsop.yml, non-blocking). After merge, tagging v0.5.0 resolves themismatch and subsequent PRs will be clean.
After merge
git tag v0.5.0 && git push origin v0.5.0release.ymltrusted-publish workflow uploads sdist/wheel to PyPIas sql-sop 0.5.0 and creates the GitHub release.