fix: vscode extension version and language id

[ymc9]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@ymc9 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4821aec and 3564afd.

📒 Files selected for processing (2)

• packages/ide/vscode/package.json (1 hunks)
• packages/language/langium-config.json (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/vscode

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR updates the VS Code extension configuration to fix version inconsistencies and language identifier alignment.

• Updates VS Code extension version from 3.0.2 to 3.0.5
• Changes language ID from "zmodel" to "zmodel-v3" to align with the V3 branding

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/language/langium-config.json	Updates language ID to include v3 suffix for consistency
packages/ide/vscode/package.json	Bumps extension version to 3.0.5

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[claude]

Claude finished @ymc9's task —— View job

---

Code Review Complete ✅

I've thoroughly reviewed this pull request. Here's my detailed analysis:

Todo List:

• Read and analyze the changed files
• Evaluate the version bump changes
• Assess the language ID modification
• Check for any potential issues or improvements
• Provide comprehensive review feedback

Review Summary

This PR makes two focused changes to align VS Code extension configuration:

✅ Code Quality & Best Practices

• Clean, targeted changes: The modifications are minimal and focused on the specific issue
• Consistent language ID: Both files now use zmodel-v3 consistently across the configuration
• Proper JSON formatting: All changes maintain correct JSON structure

✅ Changes Analysis

1. Version Bump (packages/ide/vscode/package.json:4)

• Version updated from 3.0.2 → 3.0.5
• This appears to be a patch-level increment, appropriate for bug fixes
• Note: The main project version is 3.0.0-beta.1, so the extension version being 3.0.5 suggests independent versioning

2. Language ID Standardization (packages/language/langium-config.json:5)

• Language ID changed from zmodel → zmodel-v3
• This change is consistently applied across all VS Code extension references:
  • package.json:60 - Language contribution ID
  • package.json:77 - Grammar language reference
  • package.json:84 - Activation event
  • src/extension/main.ts:46,50 - Language client configuration
  • README.md:25 - Documentation examples

🔍 Potential Issues & Considerations

• Breaking change impact: Users with existing VS Code settings referencing zmodel will need to update to zmodel-v3
• Migration path: The README.md already documents this transition well
• Backward compatibility: This intentionally breaks compatibility with v2, which is appropriate for a major version change

⚡ Performance Considerations

• No performance impact - these are static configuration changes
• Language server initialization remains unchanged

🔒 Security Concerns

• No security implications in these configuration changes
• All changes are to metadata/configuration files

🧪 Test Coverage

• No test files were modified, but these are configuration changes that don't require unit tests
• Recommendation: Manual testing should verify:
  • VS Code extension loads correctly with new language ID
  • Syntax highlighting works for .zmodel files
  • Language server activates properly

Recommendations

1. ✅ Changes look good - well-aligned and consistent
2. 📝 Consider adding to changelog if one exists for the VS Code extension
3. 🔄 Verify manual testing of VS Code extension functionality before release
4. 📚 Documentation is already up-to-date - great job on the README

Verdict: APPROVED ✅

This is a clean, well-executed fix that properly aligns the VS Code extension configuration with the v3 branding strategy.

---