chore: release v0.9.4

[basmasking]

Fixes #665

@MaskingTechnology/jitar

Summary by CodeRabbit

• Documentation

  • Updated the changelog with details for version 0.9.4, highlighting the addition of an "init" command, Windows support, and a fix for plugin loading order.

• Chores

  • Bumped version numbers to 0.9.4 for relevant packages.

[coderabbitai]

Walkthrough

The changes update version numbers from 0.9.3 to 0.9.4 across multiple package manifests and add a new entry for v0.9.4 in the changelog, detailing new features and a bug fix. No source code or public API modifications are present.

Changes

Files	Change Summary
CHANGELOG.md	Added v0.9.4 entry with new features and a fix
packages/create-jitar/package.json, packages/jitar/package.json, packages/plugin-vite/package.json	Incremented version from 0.9.3 to 0.9.4

Assessment against linked issues

Objective	Addressed	Explanation
Update packages and changelog for v0.9.4 release (#665)	✅

Suggested reviewers

• petermasking

Poem

A hop, a skip, a version hop,
v0.9.4 is at the top!
New commands and fixes, Windows cheer,
The changelog’s clear, the path sincere.
With every leap, this rabbit grins—
Another release, let joy begin!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f6e97ff and 150dff9.

📒 Files selected for processing (4)

• CHANGELOG.md (1 hunks)
• packages/create-jitar/package.json (1 hunks)
• packages/jitar/package.json (1 hunks)
• packages/plugin-vite/package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: basmasking
PR: MaskingTechnology/jitar#649
File: CHANGELOG.md:6-7
Timestamp: 2025-06-02T10:44:10.408Z
Learning: In CHANGELOG.md for the jitar project, the format `[[PR_NUMBER](link)] description (#ISSUE_NUMBER) by author` is intentionally used where the first number is the pull request ID and the second number in parentheses is the issue ID that the PR addresses. These numbers are often different and this is not an error but a deliberate formatting convention used consistently throughout the changelog.

CHANGELOG.md (1)

Learnt from: basmasking
PR: MaskingTechnology/jitar#649
File: CHANGELOG.md:6-7
Timestamp: 2025-06-02T10:44:10.408Z
Learning: In CHANGELOG.md for the jitar project, the format `[[PR_NUMBER](link)] description (#ISSUE_NUMBER) by author` is intentionally used where the first number is the pull request ID and the second number in parentheses is the issue ID that the PR addresses. These numbers are often different and this is not an error but a deliberate formatting convention used consistently throughout the changelog.

🪛 markdownlint-cli2 (0.17.2)

CHANGELOG.md

4-4: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🔇 Additional comments (4)

packages/create-jitar/package.json (1)

3-3: Version bump looks correct and consistent with the release.

No functional changes – just the semantic-version update.
Good to merge.

packages/jitar/package.json (1)

3-3: Package version aligned with monorepo release.

Nothing else altered; LGTM.

packages/plugin-vite/package.json (1)

3-3: Version updated; no other metadata touched.

Change is minimal and correct.

CHANGELOG.md (1)

1-12: Heading-level warning from markdownlint can be ignored.

The file has always used ### under a top-level release header, so the MD001 complaint isn’t a new issue. No action required.

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud