Skip to content

Conversation

@github-actions
Copy link
Contributor

🤖 I have created a release beep boop

6.1.0 (2025-11-25)

Features

Chores


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner November 25, 2025 16:41
@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 25, 2025

Release Manager

Release workflow run: https://github.com/npm/proc-log/actions/runs/19677073126

Release Checklist for v6.1.0

  • 1. Approve this PR

    gh pr review 118 -R npm/proc-log --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 118 -R npm/proc-log --squash
  • 3. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch -R npm/proc-log $(gh run list -R npm/proc-log --workspace release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 74bdb20 to 0e4193d Compare November 25, 2025 16:42
@wraithgar wraithgar merged commit 9a6975d into main Nov 25, 2025
17 checks passed
@wraithgar wraithgar deleted the release-please--branches--main branch November 25, 2025 17:11
@wraithgar
Copy link
Member

@mbtools This is live. We will do our best to get this into npm for this week's release so that you don't have to worry about including it in your PR.

@github-actions
Copy link
Contributor Author

🤖 Created releases:

🌻

@github-actions
Copy link
Contributor Author

github-actions bot commented Nov 25, 2025

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