Repository navigation
feat(canary): add upstream compatibility canary, failure alerting, and suite publishing standards (v0.2.4) - #23
Merged
MUDASSIR-75 merged 8 commits intoNov 12, 2026
Conversation
…te publishing standards
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
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.
Description
This PR implements the v0.2.4 milestone to protect LongGuard and its users from unexpected upstream framework breakages (langgraph, langchain, crewai).
Key Highlights:
Upstream Compatibility Canary (canary.yml): Runs scheduled nightly and on-demand checks against both the latest releases and lowest declared dependency bounds of upstream frameworks. Standard PR CI is now decoupled to run strictly on locked dependencies, so third-party releases will not block day-to-day development.
Automated Issue Reporting (scripts/canary_issue.py): Automatically creates or updates GitHub issues labeled compat-break when a canary run catches an upstream breaking change, with built-in deduplication to prevent duplicate issue spam.
Verified Dependency Bounds: Aligned the CrewAI lower bound in pyproject.toml to >=1.15.19 (where execution-scoped hook dispatch was introduced and verified).
Long Suite Publishing Standardization: Renamed release.yml to publish.yml to unify workflow naming across all EnDevSols Long Suite repositories (LongCache, LongParser, LongGuard), eliminating PyPI Trusted Publishing claim mismatches. Documented the setup checklist in docs/guides/publishing-standards.md.
Compatibility Matrix & Badges: Published the compatibility matrix table and live canary status badge across the documentation and README.