generated from bcgov/quickstart-openshift
-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(deps): update nestjs (major) #367
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-nestjs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
af21d2c
to
931bd88
Compare
|
48c1ad5
to
bb7e8dc
Compare
bb7e8dc
to
e3680c8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.
This PR contains the following updates:
^3.0.2
->^4.0.0
^10.3.2
->^11.0.0
^10.3.8
->^11.0.0
^3.2.2
->^4.0.0
^10.3.8
->^11.0.0
^10.3.8
->^11.0.0
^4.0.2
->^5.0.0
^10.1.1
->^11.0.0
^8.0.0
->^11.0.0
^10.2.3
->^11.0.0
^10.3.8
->^11.0.0
Release Notes
nestjs/axios (@nestjs/axios)
v4.0.0
Compare Source
What's Changed
Full Changelog: nestjs/axios@3.1.3...4.0.0
nestjs/nest-cli (@nestjs/cli)
v11.0.2
Compare Source
8aaa9df
)v11.0.1
Compare Source
bd96064
)v11.0.0
Compare Source
Migration guide: https://docs.nestjs.com/migration-guide
Features and improvements
Dependencies
nestjs/nest (@nestjs/common)
v11.0.6
Compare Source
v11.0.6 (2025-01-27)
Bug fixes
core
Committers: 1
v11.0.5
Compare Source
v11.0.5 (2025-01-23)
Bug fixes
core
Committers: 1
v11.0.4
Compare Source
v11.0.3
Compare Source
v11.0.2
Compare Source
v11.0.1
Compare Source
v11.0.0
Compare Source
nestjs/config (@nestjs/config)
v4.0.0
Compare Source
Breaking changes
The order in which configuration variables are read by the
ConfigService#get
method has been updated. The new order is:process.env
objectPreviously, validated environment variables and the
process.env
object were read first, preventing them from being overridden by internal configuration. With this update, internal configuration will now always take precedence over environment variables.Additionally, the
ignoreEnvVars
configuration option, which previously allowed disabling validation of theprocess.env
object, has been deprecated. Instead, use thevalidatePredefined
option (set tofalse
to disable validation of predefined environment variables). Predefined environment variables refer toprocess.env
variables that were set before the module was imported. For example, if you start your application withPORT=3000 node main.js
, thePORT
variable is considered predefined. However, variables loaded by theConfigModule
from a.env
file are not classified as predefined.A new
skipProcessEnv
option has also been introduced. This option allows you to prevent theConfigService#get
method from accessing theprocess.env
object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.Changelog
c2eaf04
)1c20713
)c53c63c
)nestjs/schedule (@nestjs/schedule)
v5.0.1
Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/schedule@5.0.0...5.0.1
v5.0.0
Compare Source
Breaking changes
Changelog
ae6c43c
)41d8cdb
)crypto.randomUUID()
instead ofuuid
module (58f795d
)nestjs/schematics (@nestjs/schematics)
v11.0.0
Compare Source
Release 11.0.0 (2025-01-17)
Changelog
797a384
)a4cb235
)7b205f5
)nestjs/swagger (@nestjs/swagger)
v11.0.3
Compare Source
11.0.3 (2025-01-23)
Bug fixes
Committers: 1
v11.0.2
Compare Source
Changelog
v11.0.1
Compare Source
11.0.1 (2025-01-17)
Dependencies
v11.0.0
Compare Source
11.0.0 (2025-01-16)
Breaking changes
This version is only compatible with
@nestjs/{core,common,platform-express,platform-fastify,...}
>= v11Enhancements
Dependencies
Committers: 2
v8.1.1
Compare Source
Unreleased (2025-01-10)
Bug fixes
Dependencies
Committers: 3
nestjs/terminus (@nestjs/terminus)
v11.0.0
Compare Source
v10.3.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: