Skip to content

fix(deps): update dependency @nguniversal/express-engine to v16 #4240

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

Closed

Conversation

ScriptedAlchemy
Copy link
Member

This PR contains the following updates:

Package Type Update Change
@nguniversal/express-engine dependencies major ^15.1.0 -> ^16.0.0

Release Notes

angular/universal (@​nguniversal/express-engine)

v16.2.0

Compare Source

Commit Type Description
2b0f8c2b refactor build: update critters

v16.1.3

Compare Source

@​nguniversal/common
Commit Type Description
d4be69b8 fix check for server context when doing hybrid rendering

v16.1.2

Compare Source

Commit Type Description
0c0fd610 refactor build: update critters

v16.1.1

Compare Source

v16.1.0

Compare Source

Deprecations

Commit Type Description
ccc2f52f refactor deprecate transfer http cache

v16.0.2

Compare Source

@​nguniversal/common
Commit Type Description
90d6939a fix correctly handle multiple lazy CSS files

v16.0.1

Compare Source

@​nguniversal/builders
Commit Type Description
ca8a5bb9 fix strip out newlines

v16.0.0

Compare Source

Breaking Changes

@​nguniversal/common
  • Node.js v14 support has been removed

    Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.

@​nguniversal/express-engine
Commit Type Description
3af1451a feat add standalone support to ng add
1e2b9385 feat support rendering standalone application
500f5e54 fix export default bootstrap in server template for standalone
66021f10 fix update import for template server file
@​nguniversal/builders
Commit Type Description
0481bde7 feat add support for prerendering a standalone application
@​nguniversal/common
Commit Type Description
9fbdb23c feat add CSP support for inline styles
010546e5 feat support rendering standalone application
71c2cef8 fix update TransferHttpResponse requiring body and headers
ae96fbc4 refactor remove Node.js v14 support

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@ScriptedAlchemy
Copy link
Member Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing [email protected]+sha1.572d3b6d6b0ff64f11edd1c4e8774cc7351f1089.
! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager


Copy link

github-actions bot commented Jul 8, 2024

Workflow status is failure ❌
Unfortunately test report wasn't generated, it can be if no workspaces changed. Please check the workflow run below.
Link to GitHub workflow: Github Workflow Link

@github-actions github-actions bot added the workflow-failure Workflow is failed label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
workflow-failure Workflow is failed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant