chore: release v0.9.2

[basmasking]

Fixes #641

@MaskingTechnology/jitar

Summary by CodeRabbit

• Chores
  • Updated version numbers to 0.9.2 across relevant packages.
  • Added a new changelog entry for version 0.9.2, highlighting improved resource loading.
  • Minor formatting improvement in dependency declarations.

[coderabbitai]

Walkthrough

This update increments the version numbers to 0.9.2 across several package manifests and adds a new entry for v0.9.2 in the changelog, referencing a feature update. No source code or public API changes are included.

Changes

File(s)	Change Summary
CHANGELOG.md	Added v0.9.2 entry referencing improved resource loading.
packages/create-jitar/package.json	Updated version to 0.9.2; minor formatting in devDependencies.
packages/jitar/package.json, packages/plugin-vite/package.json	Updated version to 0.9.2.

Assessment against linked issues

Objective	Addressed	Explanation
Release 0.9.2 (#641)	✅

Possibly related PRs

• chore(deps): may updates #637: Related to package version management, specifically updating and moving a dependency version in a package.json file.

Suggested reviewers

• petermasking

Poem

The numbers hop, a version new,
0.9.2 comes into view!
Changelog fresh and tidy too,
With resource loading shining through.
🐇✨
A gentle leap, a rabbit’s cheer—
Another release is finally here!

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

4-4: Adjust heading level for consistency
The changelog jumps from level 1 (#) to level 3 (###). Increment headings by one level at a time (e.g., use ## Features).

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

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

(MD001, heading-increment)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9bc2d31 and 4b3ced2.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

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

🧰 Additional context used

🪛 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 (6)

packages/jitar/package.json (1)

3-3: Version bumped to 0.9.2
The updated version aligns with the new release objectives and matches the root CHANGELOG entry.

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

3-3: Version bumped to 0.9.2
Consistent with related packages and CHANGELOG.

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

3-3: Version bumped to 0.9.2
Matches the coordinated release across all monorepo packages.

---

41-41: DevDependencies formatting tweak confirmed
Adding a space after the colon improves JSON readability without affecting functionality.

CHANGELOG.md (2)

1-2: New changelog entry for v0.9.2 added
Correctly documents the new version and release date at the top.

---

6-6: Feature entry formatting verified
The new feature listing correctly references PR #638 and original issue #608 by Peter van Vliet.