Update @willsoto/nestjs-prometheus 5.5.1 → 6.0.0 (major) #802
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
Closed in favor of #849. |
depfu
bot
deleted the
depfu/update/yarn/@willsoto/nestjs-prometheus-6.0.0
branch
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @willsoto/nestjs-prometheus (5.5.1 → 6.0.0) · Repo · Changelog
Release Notes
6.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
chore(release): 6.0.0 [skip ci]feat: support prom-client v15chore(deps): update dependency @types/chai to v4.3.7chore(deps): update typescript-eslint monorepo to v6.7.5chore(deps): update pnpm to v8.9.0chore(deps): update dependency @types/sinon to v10.0.19chore(deps): update dependency @types/node to v18.18.4chore(deps): update dependency eslint to v8.51.0chore(deps): update dependency sinon to v16.1.0chore(deps): update nest monorepo to v10.2.7chore(deps): update dependency @types/supertest to v2.0.14chore(deps): update dependency @types/sinon to v10.0.18chore(deps): update dependency @types/node to v18.18.3chore(deps): update typescript-eslint monorepo to v6.7.4chore(deps): update dependency @types/node to v18.18.1chore(deps): update dependency prettier-plugin-packagejson to v2.4.6chore(deps): update dependency @commitlint/cli to v17.7.2chore(deps): update dependency chai to v4.3.10chore(deps): update dependency @types/mocha to v10.0.2chore(deps): update dependency chai to v4.3.9chore(deps): update dependency rimraf to v5.0.5chore(deps): update pnpm to v8.8.0chore(deps): update dependency @types/node to v18.18.0chore(deps): update typescript-eslint monorepo to v6.7.3chore(deps): update dependency rimraf to v5.0.4chore(deps): update dependency @types/supertest to v2.0.13chore(deps): update dependency @types/sinon-chai to v3.2.10chore(deps): update dependency @types/sinon to v10.0.17chore(deps): update dependency semantic-release to v22.0.5chore(deps): update dependency @types/node to v18.17.19Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands