-
Notifications
You must be signed in to change notification settings - Fork 1
Claude/update product positioning 53 in9 #91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
squrtech-founder
merged 10 commits into
main
from
claude/update-product-positioning-53IN9
Jan 20, 2026
Merged
Claude/update product positioning 53 in9 #91
squrtech-founder
merged 10 commits into
main
from
claude/update-product-positioning-53IN9
Jan 20, 2026
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
- Update tagline: CLI-first data validation (not "platform with CLI") - Rewrite "What is DataCheck?" to focus on pipeline gates and CI/CD - Add "What DataCheck is NOT" section (not observability/anomaly detection) - Add "Where DataCheck Fits" section explaining data validation category - Add "How DataCheck Compares" table (vs Great Expectations, Soda, dbt) - Update pyproject.toml description and keywords - Document all changes in POSITIONING_UPDATES.md This is a positioning-only update to accurately reflect what DataCheck is today: a simple, fast validation tool for data engineers, not an enterprise observability platform.
Comprehensive 7-phase verification completed: - Phase 1: Environment & dependencies (PASS) - Phase 2: Full test suite - 629/629 tests passing (PASS) - Phase 3: Code coverage - 80.85% above 70% threshold (PASS) - Phase 4: Examples validation (PASS) - Phase 5: Static & dead code analysis (PASS) - Phase 6: Release safety checks (PASS) - Phase 7: Final verdict (CONDITIONAL APPROVAL) Release blocker identified: Version number needs update to 1.1.0 All other metrics green - codebase is production-ready.
Version Updates: - Bump version to 1.1.0 in pyproject.toml - Bump version to 1.1.0 in datacheck/__init__.py CHANGELOG: - Add comprehensive v1.1.0 release notes - Document removal of enterprise features (API, ML monitoring) - Document simplified Airflow/dbt integrations - Add migration guide for v1.0.0 users - Add breaking changes notice - Document all core features remain unchanged CI/CD Fixes: - Remove --extras "api" from ci.yml (API module removed) - Remove --extras "api" from release.yml - Remove --extras "api" from auto-release.yml - Workflows now install without extras Release Highlights: - 14,523 lines of code removed - Test suite: 629 tests passing (100% pass rate) - Code coverage: 80.85% (above 70% threshold) - Clear product positioning as CLI-first validation tool - All core validation features unchanged This release will trigger auto-release workflow when merged to main.
- Remove references to DataCheckProfilingOperator (removed) - Remove references to DataCheckSensor (removed) - Focus on 3 remaining operators: DataCheckOperator, DataCheckValidateOperator, DataCheckSchemaOperator - Emphasize CLI via BashOperator as recommended approach - Update examples to match simplified integration - Remove references to removed DAG factory and complex sensors
- Remove 'api' and 'ml' extras from installation guide - Update available extras table (only postgresql, mysql, mssql, cloud, all) - Remove reference to non-existent 'REST API Dashboard' module from dbt integration - Update related modules links to point to existing modules
Removed: - PRODUCTION_SECURITY_GUIDE.md (REST API security guide - no longer applicable) Updated README_PYPI.md: - Changed tagline to 'CLI-first data validation tool for data engineers' - Removed 'Enterprise features' language - Added 'What is DataCheck?' section - Added detailed validation rules table with examples - Added use cases section (pipeline gates, CI/CD, etc.) - Added exit codes documentation - Added Python API usage example - Expanded links section Updated SECURITY.md: - Removed references to REST API authentication and CORS - Removed reference to deleted PRODUCTION_SECURITY_GUIDE.md - Added v1.1.x to supported versions - Reorganized into focused sections (database, cloud, plugins, CI/CD) - Added data privacy best practices - Updated security features to reflect CLI-first tool - Added third-party dependencies list All documentation now aligns with CLI-first positioning.
Removed temporary release preparation docs: - RELEASE_READINESS_REPORT_v1.1.0.md (internal verification) - v1.1.0_RELEASE_SUMMARY.md (internal deployment guide) CHANGELOG.md contains all user-facing release information.
pyproject.toml was updated to remove api, ml, and streaming extras. Regenerated lock file to match current dependencies.
yash-chauhan-dev
approved these changes
Jan 20, 2026
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
Type of Change
Related Issue
Fixes #(issue number)
Related to #(issue number)
Motivation and Context
Changes Made
Testing
How Has This Been Tested?
Test Configuration
Python Version(s):
Operating System(s):
Data Formats Tested:
Screenshots (if applicable)
Checklist
Code Quality
Testing
Documentation
Git
Breaking Changes
Does this introduce a breaking change?
If yes, please describe:
Additional Notes
For Reviewers
Focus areas for review:
Questions for reviewers:
By submitting this pull request, I confirm that: