chore: prepare for release v0.11.1

[basmasking]

Fixes #790

Changes proposed in this pull request:

• updated examples to use latest compatible version of jitar
• bumped the version of all the packages
• updated docs for development

@MaskingTechnology/jitar

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a36524fa-46a7-4bc7-9128-eab5e8dc7e62

📥 Commits

Reviewing files that changed from the base of the PR and between b53cb79 and 3ad4b3f.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (33)

• CHANGELOG.md
• DEVELOPMENT.md
• examples/access-protection/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
• package.json
• packages/analysis/package.json
• packages/build/package.json
• packages/cli/package.json
• packages/configuration/package.json
• packages/errors/package.json
• packages/execution/package.json
• packages/health/package.json
• packages/http/package.json
• packages/init/package.json
• packages/jitar/package.json
• packages/logging/package.json
• packages/middleware/package.json
• packages/plugin-vite/package.json
• packages/runtime/package.json
• packages/scheduling/package.json
• packages/serialization/package.json
• packages/services/package.json
• packages/sourcing/package.json
• packages/validation/package.json
• tools/eslint-plugin/package.json

---

Summary by CodeRabbit

• Chores
  • Released version 0.11.1 across all packages.
  • Updated CHANGELOG with new release entries for v0.11.0 and v0.10.6.
  • Updated development workflow documentation to require Node.js 22.9+ and npm 11.x+, and adjusted build/release procedures.
  • Updated example package dependencies to use compatible version ranges.

Walkthrough

Release preparation for v0.11.1: all monorepo package versions are bumped from 0.11.0 to 0.11.1, CHANGELOG.md receives new v0.11.0 and v0.10.6 sections, DEVELOPMENT.md workflow instructions are revised, and all example jitar dependencies are loosened from a pinned version to ^0.11.0.

Changes

v0.11.1 Release Preparation

Layer / File(s)	Summary
Changelog and development workflow updates CHANGELOG.md, DEVELOPMENT.md	CHANGELOG.md gains v0.11.0 (two dated subsections) and v0.10.6 release sections at the top. DEVELOPMENT.md raises the Node.js requirement to 22.9+/npm 11.x+, switches installation to npm ci, removes the npm run changeset step, and rewrites publishing instructions to use npm run version $VERSION with a manually triggered workflow post-merge.
Monorepo package version bumps to 0.11.1 package.json, packages/*/package.json, tools/eslint-plugin/package.json	Root and all 20 workspace package manifests have their version field incremented from 0.11.0 to 0.11.1.
Example jitar dependency loosened to caret range examples/*/package.json	All 10 example package manifests change the jitar dependency from pinned 0.11.0 to ^0.11.0, allowing compatible patch/minor updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• MaskingTechnology/jitar#677: Previous release chore that similarly bumped CHANGELOG.md and version fields across the same set of package manifests.
• MaskingTechnology/jitar#779: Immediately preceding release that bumped the same monorepo manifests from 0.10.8 → 0.11.0, the baseline version this PR increments from.
• MaskingTechnology/jitar#706: Also modifies DEVELOPMENT.md around the same changeset creation and release/publishing workflow steps.

Suggested reviewers

• petermasking

🐇 A hop, a skip, a version new,
From .0 to .1 we flew!
The changelog bloomed, the docs grew neat,
With caret ranges — oh, what a treat!
🌱 v0.11.1 is complete! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: preparing the jitar project for v0.11.1 release.
Description check	✅ Passed	The description follows the template structure, includes the linked issue reference, outlines three main changes clearly, and includes the team mention.
Linked Issues check	✅ Passed	All proposed changes—updating examples to compatible versions, bumping package versions to 0.11.1, and updating development documentation—align with preparing for release v0.11.1 as specified in issue #790.
Out of Scope Changes check	✅ Passed	All changes directly support the release preparation objective: documentation updates (CHANGELOG, DEVELOPMENT), version bumps across all packages, and example dependency updates are all in-scope for v0.11.1 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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