chore: release v0.10.2

[basmasking]

Fixes #708

Changes proposed in this pull request:

• updated versions to 0.10.2
• released to npm

@MaskingTechnology/jitar

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Version bumped to 0.10.2
  • Updated all package dependencies and project templates to maintain consistency

Walkthrough

A version bump release updating the jitar framework from 0.10.1 to 0.10.2 across all package.json files in the repository, including example projects, core packages, and CLI templates. Root package version updated from 0.9.3 to 0.10.2.

Changes

Cohort / File(s)	Summary
Root package version package.json	Version bumped from 0.9.3 to 0.10.2
Core packages packages/jitar/package.json, packages/create-jitar/package.json, packages/plugin-vite/package.json	Version bumped from 0.10.1 to 0.10.2
Example projects examples/access-protection/package.json, examples/cors/package.json, examples/data-transportation/package.json, examples/error-handling/package.json, examples/health-checks/package.json, examples/hello-world/package.json, examples/load-balancing/package.json, examples/middleware/package.json, examples/multi-version/package.json, examples/resources/package.json, examples/segmentation/package.json	jitar dependency bumped from 0.10.1 to 0.10.2
CLI templates packages/init/templates/backend/package.json, packages/init/templates/react/package.json, packages/init/templates/vue/package.json	jitar dependency bumped from ^\0.10.1 to ^\0.10.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• All changes are straightforward version bumps with no logic modifications
• Homogeneous pattern repeated across all files (simple find-and-replace updates)
• No behavioral or structural changes introduced

Possibly related PRs

• PR #699 — Previous patch release version bump from 0.10.0 to 0.10.1 across the same set of package.json files
• PR #677 — Similar version bump PR updating core packages (jitar, plugin-vite, create-jitar)
• PR #706 — Repository-wide dependency bump PR affecting package.json files across examples and packages

Suggested reviewers

• petermasking

Poem

🐰 Hop, hop, the versions rise,
From 0.10.1 to 0.10.2 skies!
Each package takes its turn to climb,
A release in perfect, synchronized time! ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: release v0.10.2' clearly summarizes the main change—a version release bump across all package files.
Description check	✅ Passed	The description follows the template with issue reference #708, lists changes (version updates to 0.10.2 and npm release), and mentions the team.
Linked Issues check	✅ Passed	The PR successfully addresses the linked issue #708 by updating all package versions to 0.10.2 and preparing for npm release as required.
Out of Scope Changes check	✅ Passed	All changes are in-scope: only version updates from 0.10.1 to 0.10.2 across package.json files, directly aligned with the release objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 708-release-v0102

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b9e9bf6 and 3a6c64b.

📒 Files selected for processing (18)

• examples/access-protection/package.json (1 hunks)
• examples/cors/package.json (1 hunks)
• examples/data-transportation/package.json (1 hunks)
• examples/error-handling/package.json (1 hunks)
• examples/health-checks/package.json (1 hunks)
• examples/hello-world/package.json (1 hunks)
• examples/load-balancing/package.json (1 hunks)
• examples/middleware/package.json (1 hunks)
• examples/multi-version/package.json (1 hunks)
• examples/resources/package.json (1 hunks)
• examples/segmentation/package.json (1 hunks)
• package.json (1 hunks)
• packages/create-jitar/package.json (1 hunks)
• packages/init/templates/backend/package.json (1 hunks)
• packages/init/templates/react/package.json (1 hunks)
• packages/init/templates/vue/package.json (1 hunks)
• packages/jitar/package.json (1 hunks)
• packages/plugin-vite/package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (5)

📓 Common learnings

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/init/templates/jitar-only/package.json:6-6
Timestamp: 2025-07-28T19:38:55.816Z
Learning: In jitar templates (like packages/init/templates/jitar-only/package.json), the jitar build command doesn't produce a .jitar folder. Templates use a jitar.json configuration where both source and target point to "./dist", unlike examples where a .jitar folder may be generated.

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/init/templates/jitar-only/package.json:6-6
Timestamp: 2025-07-28T19:38:55.816Z
Learning: Jitar templates use a jitar.json configuration structure with "source": "./dist", "target": "./dist", and "segments": "./segments", where the CLI rewrites files from the dist folder back to the dist folder, and segment configuration files are found in the segments folder.

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/validation/package.json:16-16
Timestamp: 2025-07-28T19:44:53.054Z
Learning: In the jitar monorepo, standardized tooling dependencies like rimraf, vitest, and typescript are intentionally defined once at the root level package.json and rely on npm hoisting rather than being duplicated in each individual package's package.json file. Package-specific dependencies should be in individual package.json files, but common tooling should be centralized.

📚 Learning: 2025-07-28T19:38:55.816Z

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/init/templates/jitar-only/package.json:6-6
Timestamp: 2025-07-28T19:38:55.816Z
Learning: In jitar templates (like packages/init/templates/jitar-only/package.json), the jitar build command doesn't produce a .jitar folder. Templates use a jitar.json configuration where both source and target point to "./dist", unlike examples where a .jitar folder may be generated.

Applied to files:

• packages/init/templates/react/package.json
• examples/data-transportation/package.json
• packages/init/templates/backend/package.json
• examples/hello-world/package.json
• examples/multi-version/package.json
• examples/resources/package.json
• examples/access-protection/package.json
• examples/health-checks/package.json
• packages/jitar/package.json
• examples/segmentation/package.json
• examples/load-balancing/package.json
• examples/error-handling/package.json
• packages/create-jitar/package.json
• examples/cors/package.json
• examples/middleware/package.json
• package.json
• packages/init/templates/vue/package.json

📚 Learning: 2025-07-28T19:38:55.816Z

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/init/templates/jitar-only/package.json:6-6
Timestamp: 2025-07-28T19:38:55.816Z
Learning: Jitar templates use a jitar.json configuration structure with "source": "./dist", "target": "./dist", and "segments": "./segments", where the CLI rewrites files from the dist folder back to the dist folder, and segment configuration files are found in the segments folder.

Applied to files:

• packages/init/templates/react/package.json
• examples/data-transportation/package.json
• packages/init/templates/backend/package.json
• examples/hello-world/package.json
• examples/multi-version/package.json
• examples/resources/package.json
• examples/access-protection/package.json
• examples/health-checks/package.json
• packages/jitar/package.json
• examples/segmentation/package.json
• examples/load-balancing/package.json
• examples/error-handling/package.json
• packages/create-jitar/package.json
• examples/cors/package.json
• examples/middleware/package.json
• package.json
• packages/init/templates/vue/package.json

📚 Learning: 2025-07-28T19:44:53.054Z

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 678
File: packages/validation/package.json:16-16
Timestamp: 2025-07-28T19:44:53.054Z
Learning: In the jitar monorepo, standardized tooling dependencies like rimraf, vitest, and typescript are intentionally defined once at the root level package.json and rely on npm hoisting rather than being duplicated in each individual package's package.json file. Package-specific dependencies should be in individual package.json files, but common tooling should be centralized.

Applied to files:

• packages/init/templates/react/package.json
• examples/data-transportation/package.json
• packages/init/templates/backend/package.json
• examples/hello-world/package.json
• examples/multi-version/package.json
• examples/resources/package.json
• examples/access-protection/package.json
• examples/health-checks/package.json
• examples/segmentation/package.json
• examples/load-balancing/package.json
• examples/error-handling/package.json
• examples/cors/package.json
• examples/middleware/package.json
• package.json
• packages/init/templates/vue/package.json

📚 Learning: 2025-11-01T12:49:12.253Z

Learnt from: basmasking
Repo: MaskingTechnology/jitar PR: 706
File: examples/resources/package.json:11-14
Timestamp: 2025-11-01T12:49:12.253Z
Learning: Examples in the jitar monorepo (files under examples/ directory) are not included in the workspace setup, so npm hoisting does not work for them. Unlike packages, examples must declare their own devDependencies (like rimraf, typescript, etc.) directly in their package.json files.

Applied to files:

• packages/init/templates/react/package.json
• examples/data-transportation/package.json
• packages/init/templates/backend/package.json
• examples/hello-world/package.json
• examples/multi-version/package.json
• examples/resources/package.json
• examples/access-protection/package.json
• examples/health-checks/package.json
• examples/segmentation/package.json
• examples/load-balancing/package.json
• examples/error-handling/package.json
• examples/cors/package.json
• examples/middleware/package.json
• package.json
• packages/init/templates/vue/package.json

🔇 Additional comments (19)

package.json (1)

3-3: Verify root monorepo version bump rationale.

The root version jumps from 0.9.3 to 0.10.2, skipping what would typically be 0.10.0 and 0.10.1. This appears inconsistent with semantic versioning conventions. Clarify whether this is intentional (e.g., root version tracks something different from the jitar package version) or should align with standard incrementing.

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

3-3: Version bump looks good.

Patch-level version increment from 0.10.1 to 0.10.2 is appropriate and consistent with expected release versioning.

examples/middleware/package.json (1)

16-16: Dependency version update is correct.

Patch-level bump to jitar 0.10.2 is appropriate. Example packages correctly use exact version pinning.

examples/data-transportation/package.json (1)

19-19: Dependency version update is correct.

Patch-level bump to jitar 0.10.2 is appropriate and consistent with other examples in this release.

examples/health-checks/package.json (1)

16-16: Dependency version update is correct.

Patch-level bump to jitar 0.10.2 is appropriate and maintains consistency across all examples.

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

3-3: Version bump looks good.

Patch-level version increment from 0.10.1 to 0.10.2 is appropriate for a public plugin package. Dependencies and peer configurations remain stable.

examples/hello-world/package.json (1)

16-16: Dependency version update is correct.

Patch-level bump to jitar 0.10.2 is consistent with the release across all examples.

examples/cors/package.json (1)

19-19: Dependency version update is correct.

Patch-level bump to jitar 0.10.2 is consistent with the release across all examples.

examples/error-handling/package.json (1)

19-19: Version bump looks good.

The jitar dependency is correctly updated to 0.10.2, aligning with the release.

packages/jitar/package.json (1)

3-3: Core package version correctly updated.

The main jitar package version is properly bumped to 0.10.2 for the release.

examples/segmentation/package.json (1)

19-19: Version bump consistent across examples.

Jitar dependency correctly updated to 0.10.2.

packages/init/templates/vue/package.json (1)

14-19: Potential version mismatch: @jitar/plugin-vite not updated.

Line 14 updates jitar to ^0.10.2, but line 19 leaves @jitar/plugin-vite at ^0.10.1. If plugin-vite was also released as 0.10.2 as part of this release, it should be updated for consistency and to ensure template users get compatible versions.

Please verify: Was @jitar/plugin-vite bumped to 0.10.2 as part of this release? If so, apply this fix:

   "devDependencies": {
     "@types/node": "^24.9.2",
-    "@jitar/plugin-vite": "^0.10.1",
+    "@jitar/plugin-vite": "^0.10.2",
     "@vitejs/plugin-vue": "^6.0.1",

examples/multi-version/package.json (1)

16-16: Version bump consistent.

Jitar dependency correctly updated to 0.10.2.

examples/load-balancing/package.json (1)

19-19: Version bump consistent.

Jitar dependency correctly updated to 0.10.2.

examples/resources/package.json (1)

16-16: Version bump consistent.

Jitar dependency correctly updated to 0.10.2.

packages/init/templates/backend/package.json (1)

13-13: Version bump consistent.

Jitar dependency correctly updated to ^0.10.2 for the backend template.

packages/init/templates/react/package.json (2)

19-19: Verify whether @jitar/plugin-vite should be updated to 0.10.2.

The jitar dependency at line 14 has been updated to ^0.10.2, but @jitar/plugin-vite at line 19 remains at ^0.10.1. Given that the PR objectives state "Updates package versions to 0.10.2" and the AI summary indicates packages/plugin-vite is part of the PR scope, this may be an unintended omission.

Please confirm whether:

1. @jitar/plugin-vite 0.10.1 is intentionally retained for compatibility with jitar 0.10.2, or
2. This should be updated to ^0.10.2 to align with the release.

---

14-14: Version specifier inconsistency across repository.

This file uses a caret (^) specifier for jitar (^0.10.2), while examples/access-protection/package.json uses an exact pinned version (0.10.2). For a release PR with a specific version bump to 0.10.2, consider verifying that the versioning strategy is consistent across templates and examples or is intentional by design.

examples/access-protection/package.json (1)

19-19: LGTM!

The jitar dependency has been correctly updated to 0.10.2, aligning with the PR's release objectives.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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