Skip to content

chore: release main #1376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2025
Merged

chore: release main #1376

merged 1 commit into from
Apr 9, 2025

Conversation

next-team
Copy link
Contributor

@next-team next-team commented Mar 31, 2025

🪨 I've created a release for you

client-metrics-web: 0.1.0

0.1.0 (2025-04-09)

Features

  • add a new client-metrics-web package (23c1ffc)
crash-handler: 5.0.3

5.0.3 (2025-04-09)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @dotcom-reliability-kit/log-error bumped from ^5.0.2 to ^5.0.3
log-error: 5.0.3

5.0.3 (2025-04-09)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @dotcom-reliability-kit/logger bumped from ^4.1.0 to ^4.1.1
logger: 4.1.1

4.1.1 (2025-04-09)

Documentation Changes

  • improve mock logger sample (82c2d19)
middleware-log-errors: 5.0.3

5.0.3 (2025-04-09)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @dotcom-reliability-kit/log-error bumped from ^5.0.2 to ^5.0.3
middleware-render-error-info: 6.0.3

6.0.3 (2025-04-09)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @dotcom-reliability-kit/log-error bumped from ^5.0.2 to ^5.0.3
opentelemetry: 3.0.5

3.0.5 (2025-04-09)

Bug Fixes

  • bump @opentelemetry/auto-instrumentations-node (9554b0f)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @dotcom-reliability-kit/log-error bumped from ^5.0.2 to ^5.0.3
      • @dotcom-reliability-kit/logger bumped from ^4.1.0 to ^4.1.1

This PR was generated with Release Please. See documentation.

@rowanmanning
Copy link
Member

Not gonna merge immediately as it's just a documentation change. Will queue up a few more changes first

@next-team next-team force-pushed the release-please--branches--main branch 6 times, most recently from 1a87110 to 510ed73 Compare April 9, 2025 07:48
@next-team next-team force-pushed the release-please--branches--main branch from 510ed73 to 0a815fb Compare April 9, 2025 12:46
@next-team next-team force-pushed the release-please--branches--main branch from 0a815fb to 4228052 Compare April 9, 2025 13:56
@rowanmanning rowanmanning enabled auto-merge (rebase) April 9, 2025 13:58
@rowanmanning rowanmanning merged commit 15a0554 into main Apr 9, 2025
11 checks passed
@rowanmanning rowanmanning deleted the release-please--branches--main branch April 9, 2025 13:59
@next-team
Copy link
Contributor Author

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.

2 participants