Skip to content
This repository was archived by the owner on Jul 3, 2026. It is now read-only.

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

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

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

Conversation

@peter-svensson

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

Copy link
Copy Markdown
Member

🤖 I have created a release beep boop

0.0.1 (2026-06-29)

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)
  • deps: pin dependencies (#16) (dd3ae17)
  • 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

codecov Bot commented Mar 9, 2026

Copy link
Copy Markdown

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
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch 2 times, most recently from 15cf8f3 to bf7983e Compare May 4, 2026 01:57
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch 2 times, most recently from 9068c88 to 03612b1 Compare May 18, 2026 00:57
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from 03612b1 to 868888e Compare May 21, 2026 02:07
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from 868888e to ce5284f Compare June 3, 2026 02:09
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from ce5284f to 8fba56b Compare June 10, 2026 05:47
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from 8fba56b to a6f6be1 Compare June 21, 2026 22:27
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from a6f6be1 to fda2519 Compare June 29, 2026 10:59
@peter-svensson peter-svensson force-pushed the release-please--branches--main--components--messaging-nats branch from fda2519 to e3709ae Compare June 29, 2026 14:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant