Update @willsoto/nestjs-prometheus 5.3.0 → 5.5.0 (minor) #790
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @willsoto/nestjs-prometheus (5.3.0 → 5.5.0) · Repo · Changelog
Release Notes
5.5.0
5.4.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 50 commits:
chore(release): 5.5.0 [skip ci]
feat: allow the module to be registered as global
chore(deps): update dependency @types/node to v18.17.16
chore(deps): update dependency sinon to v16
chore(deps): update typescript-eslint monorepo to v6.7.0
chore(deps): update pnpm to v8.7.5
chore(deps): update nest monorepo to v10.2.5
chore(deps): update dependency semantic-release to v21.1.1
chore: better test names
chore(release): 5.4.0 [skip ci]
feat: add prefix to all injected metrics
chore(deps): update dependency eslint to v8.49.0
chore(deps): update dependency @types/node to v18.17.15
chore(deps): update pnpm to v8.7.4
chore(deps): update typescript-eslint monorepo to v6.6.0
chore(deps): update dependency @types/chai-as-promised to v7.1.6
chore(deps): update dependency @types/chai to v4.3.6
chore(deps): update dependency @types/node to v18.17.14
chore(deps): update dependency @types/node to v18.17.13
chore(deps): update nest monorepo to v10.2.4
chore(deps): update pnpm to v8.7.1
chore(deps): update dependency @nestjs/cli to v10.1.17
chore(deps): update nest monorepo to v10.2.3
chore(deps): update dependency prettier to v3.0.3
chore(deps): update typescript-eslint monorepo to v6.5.0
chore(deps): update nest monorepo to v10.2.2
chore(deps): update dependency @types/node to v18.17.12
chore(deps): update pnpm to v8.7.0
chore(deps): update dependency eslint to v8.48.0
chore(deps): update dependency @nestjs/cli to v10.1.16
chore(deps): update dependency @types/node to v18.17.11
chore(deps): update dependency typescript to v5.2.2
chore(deps): update dependency chai to v4.3.8
chore(deps): update dependency @nestjs/cli to v10.1.15
chore(deps): update dependency @types/node to v18.17.9
chore(deps): update dependency @nestjs/cli to v10.1.14
chore(deps): update nest monorepo to v10.2.1
chore(deps): update dependency @types/node to v18.17.8
chore(deps): update dependency @types/express-serve-static-core to v4.17.36
chore(deps): update dependency @nestjs/cli to v10.1.13
chore(deps): update dependency @types/node to v18.17.7
chore(deps): update typescript-eslint monorepo to v6.4.1
chore(deps): update dependency lint-staged to v14.0.1
chore(deps): update nest monorepo to v10.2.0
chore(deps): update dependency @types/node to v18.17.6
chore(deps): update dependency @nestjs/cli to v10.1.12
chore(deps): update dependency prettier to v3.0.2
chore(deps): update typescript-eslint monorepo to v6.4.0
chore(deps): update dependency lint-staged to v14
chore(deps): update dependency lint-staged to v13.3.0
Depfu 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