Skip to content

chore(main): release messaging-nats 0.0.1#14

Open
peter-svensson wants to merge 1 commit intomainfrom
release-please--branches--main--components--messaging-nats
Open

chore(main): release messaging-nats 0.0.1#14
peter-svensson wants to merge 1 commit intomainfrom
release-please--branches--main--components--messaging-nats

Conversation

@peter-svensson
Copy link
Copy Markdown
Member

@peter-svensson peter-svensson commented Mar 9, 2026

🤖 I have created a release beep boop

0.0.1 (2026-04-01)

Features

  • add automerge workflow for PRs (#3) (2be3c12)
  • initial NATS transport implementation (a045242)

Bug Fixes

  • add packages:read permission for GitHub Packages auth (4b1bd37)
  • address code review findings (#15) (3645d6b)
  • ci: add job name to match required status check (#6) (5f264e4)
  • configure GitHub Packages registry and generate lockfile (beeb8e8)
  • remove synchronize trigger from review gate (#13) (2cf31ef)
  • replace broken NATS health check with port wait step (#8) (0900390)
  • review gate allows owner PRs, requires approval for others (0b6eae3)
  • set release-as 0.0.1 for initial release (f866758)
  • update npm package name to match org (#2) (c0a7863)
  • use RELEASE_PLEASE_TOKEN for release-please action (#10) (4e6278c)

This PR was generated with Release Please. See documentation.

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from 7b42db3 to 3cb7c9b Compare April 1, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant