chore(metrics): trigger release - #576
Merged
Merged
Conversation
The metrics package was skipped in the last release: the workflow bumped package.json to 5.0.0, but 5.0.0 was already on npm from an earlier publish, so the publish step treated it as done. As a result the @prometheus-io/client migration (#575) is not on npm, and the published 5.0.0 still declares a prom-client peer dependency. Touching packages/metrics/README.md puts the package back into the release matrix so it gets a fresh version. Claude-Session: https://claude.ai/code/session_01XJphWzj3io8FfcZSkLtLQL
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe change adds trailing blank lines to ChangesMetrics README
Estimated code review effort: 1 (Trivial) | ~2 minutes ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The metrics package was skipped in the last release. The workflow bumped
packages/metrics/package.jsonto 5.0.0, but 5.0.0 was already on npm from an earlier publish (2026-08-10), so the publish step saw the version as existing and skipped it.Result: the
@prometheus-io/clientmigration (#575) never reached npm. The published 5.0.0 still declaresprom-clientas a peer dependency, andlatestpoints at 4.4.4.This PR adds a trailing newline to
packages/metrics/README.mdso the paths filter inpublish.ymlputs metrics back into the release matrix.Needs a version-bump label to actually publish.
release-same-versionwould skip again, since 5.0.0 is taken.https://claude.ai/code/session_01XJphWzj3io8FfcZSkLtLQL
Summary by CodeRabbit