Triggering release

[CarlosGamero]

There is a type issue caused by compiled code, so we need to trigger a release to recompile with the updated types.

(tsgo) TS2322: Type
import('/Users/carlos.gamero@lokalise.com/development/Node/autopilot/node_modules/@message-queue-toolkit/core/dist/events/EventRegistry').EventRegistry<SupportedEvents>
is not assignable to type
import('/Users/carlos.gamero@lokalise.com/development/Node/autopilot/node_modules/@message-queue-toolkit/sns/node_modules/@message-queue-toolkit/core/dist/events/EventRegistry').EventRegistry<SupportedEvents>

Summary by CodeRabbit

• Documentation

  • Updated README files in AMQP, GCP Pub/Sub, SNS, and SQS packages with formatting improvements and clarifications.

• Chores

  • Updated dependency version specifications across multiple packages for workspace consistency.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

Six package.json files have their @message-queue-toolkit/core dependency specifiers changed from wildcard (*) or version ranges to workspace:*; the kafka package additionally bumps its peerDependencies minimum to >=26.1.1. Four READMEs receive minor text reflow or a new cross-reference note.

Changes

Monorepo maintenance

Layer / File(s)	Summary
package.json workspace dependency alignment packages/gcs-payload-store/package.json, packages/kafka/package.json, packages/metrics/package.json, packages/outbox-core/package.json, packages/redis-message-deduplication-store/package.json, packages/s3-payload-store/package.json	@message-queue-toolkit/core (and @message-queue-toolkit/schemas in outbox-core) dependency specifiers changed from * or >=x.y.z to workspace:*. kafka's peerDependencies minimum is also updated to >=26.1.1.
README text formatting packages/amqp/README.md, packages/gcp-pubsub/README.md, packages/sns/README.md, packages/sqs/README.md	amqp README adds a line pointing to the root README. gcp-pubsub, sns, and sqs READMEs have introductory sentence line wrapping adjusted with no content changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• kibertoad

Poem

🐇 Hop hop, the wildcards are gone,
workspace:* now leads us along!
The READMEs got a tidy trim,
A line break here, a note on a whim.
The monorepo hops neat and true —
✨ All in a day's work for a bunny like you!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Triggering release' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the changeset's primary purpose.	Replace with a more specific title describing the core changes, such as 'chore: update workspace dependencies and fix type compatibility' or 'chore: update to workspace:* dependency protocol'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/trigger_release

---

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