chore(release): release in ci

[inula-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

openinula@1.0.1

Patch Changes

• 3e17f33: fix: export Action type

Summary by CodeRabbit

• Bug Fixes

  • Correctly export the Action type in the core package (v1.0.1).

• Chores

  • Bumped package versions to 1.0.1 across related packages.
  • Aligned peer and dev dependency requirements to openinula 1.0.1.
  • Removed obsolete release metadata.

• Documentation

  • Updated changelog with 1.0.1 patch notes.

[coderabbitai]

Walkthrough

Version bump to openinula 1.0.1 across packages. Updated peer/dev dependency ranges in inula-intl and inula-router. Bumped versions for inula and its scripts package. Added a 1.0.1 changelog entry noting “fix: export Action type.” Removed a redundant changeset entry.

Changes

Cohort / File(s)	Change Summary
Dependency alignment (openinula 1.0.1) packages/inula-intl/package.json, packages/inula-router/package.json	Update peerDependencies from >=0.0.1 to >=1.0.1 and devDependencies from ^0.1.1 to ^1.0.1 for openinula.
Release version bumps packages/inula/package.json, packages/inula/scripts/package.json	Increment package version from 1.0.0 to 1.0.1.
Changelog update packages/inula/CHANGELOG.md	Add 1.0.1 entry with “fix: export Action type.”
Changeset cleanup .changeset/twelve-cobras-tie.md	Remove changeset file referencing the Action type export fix.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: first major version for openinula #34 — Prior release metadata updates around version 1.0.0 for the same package set.
• chore: patch eco-lib #33 — Related release metadata adjustments for openinula and associated packages.

Poem

I thump my paws—version hops anew,
From 1.0.0 to .1 we flew.
Dependencies align, tidy and bright,
Changelog whispers the Action’s light.
A shed snakeskin changeset fades—
Onward we bound through verdant glades! 🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/master

---

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.

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

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

packages/inula/package.json (1)

7-7: Version bump looks good; consider updating Node engine floor in a follow-up.

Approved. As a minor housekeeping follow-up (not blocking), "engines.node": ">=0.10.0" is unrealistically low for modern toolchains; consider raising to something like ">=14" or ">=16" to avoid accidental installs on unsupported runtimes.

packages/inula-router/package.json (1)

28-28: Deps aligned to 1.0.1; tighten peer range to avoid future-major breakage.

Approved. To prevent accidental compatibility claims for 2.x, consider constraining peer range to the current major.

Apply if desired:

   "devDependencies": {
-    "openinula": "^1.0.1",
+    "openinula": "^1.0.1",
   ...
   "peerDependencies": {
-    "openinula": ">=1.0.1"
+    "openinula": ">=1.0.1 <2"
   },

Also applies to: 39-39

packages/inula/CHANGELOG.md (1)

3-8: Changelog entry is clear and scoped.

Looks good. Optional: include a brief note or link on what “export Action type” unblocks for consumers (e.g., TS import path), to aid release notes readers.

packages/inula-intl/package.json (1)

27-27: Peer/dev dependency bumps aligned; consider semver-safe peer constraint.

Approved. Similar to router, you may want to cap peers to the 1.x line.

Optional change:

   "peerDependencies": {
-    "openinula": ">=1.0.1"
+    "openinula": ">=1.0.1 <2"
   },
   "devDependencies": {
-    "openinula": "^1.0.1",
+    "openinula": "^1.0.1",

Also applies to: 31-31

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3e17f33 and 90aba58.

📒 Files selected for processing (6)

• .changeset/twelve-cobras-tie.md (0 hunks)
• packages/inula-intl/package.json (1 hunks)
• packages/inula-router/package.json (2 hunks)
• packages/inula/CHANGELOG.md (1 hunks)
• packages/inula/package.json (1 hunks)
• packages/inula/scripts/package.json (1 hunks)

💤 Files with no reviewable changes (1)

• .changeset/twelve-cobras-tie.md

🔇 Additional comments (1)

packages/inula/scripts/package.json (1)

7-7: Template package.json version aligned; verify publish pipeline uses this template.

Approved. Please confirm CI/build copies this file into packages/inula/build/inula/package.json before npm publish (since publishConfig.directory points there), and that the "exports"/"types" fields match the built layout.