chore: Remove explicit MemberJunction 3.0 version references from code#1962
Merged
chore: Remove explicit MemberJunction 3.0 version references from code#1962
Conversation
…rce code Version-specific references in comments, console.logs, and READMEs are unnecessary and become stale as the project evolves. This removes "3.0" from labels/branding while preserving version references in migration docs and forward-looking design notes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: b5a9ca8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 169 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Claude finished @rkihm-BC's task —— View job Todo List:
SummaryI've completed the review of this PR as requested. The PR contains only TypeScript and README file changes that remove "3.0" version references from the codebase. There are no SQL migration files to review, so there are no INSERT statements or spCreate* stored procedures that need checking for proper UUID handling. The review has been submitted as a non-blocking COMMENT review. |
Contributor
✅ Dependency Check ResultsAll dependencies are properly declared! No missing dependencies detected in this PR. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
SQL Migration Review
I've reviewed this PR specifically for SQL migration files as requested.
Finding: This PR contains no SQL migration files. All 9 changed files are TypeScript source files and README documentation files that remove "3.0" version references from comments and console output.
Since there are no SQL files in the migrations/ directory to review, there are no INSERT statements or spCreate* stored procedures to check for proper UUID handling.
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.
Version-specific references in comments, console.logs, and READMEs are unnecessary and become stale as the project evolves. This removes "3.0" from labels/branding while preserving version references in migration docs and forward-looking design notes.