-
Notifications
You must be signed in to change notification settings - Fork 827
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
build(deps): bump jasmine from 4.6.0 to 5.0.1 in /uaa #2364
Conversation
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/185381837 The labels on this github issue will be updated when the story is started. |
@dependabot rebase |
3f9eb8c
to
7cfa0bd
Compare
Bumps [jasmine](https://github.com/jasmine/jasmine-npm) from 4.6.0 to 5.0.1. - [Release notes](https://github.com/jasmine/jasmine-npm/releases) - [Changelog](https://github.com/jasmine/jasmine-npm/blob/main/RELEASE.md) - [Commits](jasmine/jasmine-npm@v4.6.0...v5.0.1) --- updated-dependencies: - dependency-name: jasmine dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
7cfa0bd
to
9498e5b
Compare
Looks like there is a
/tmp/build/9d457a1d/uaa/uaa/node_modules/minimatch/dist/cjs/ast.js:86 SyntaxError: Unexpected token '(' |
This requires a node upgrade. Release notes show it is tested for node 18 or 20. |
Superseded by #2378. |
Bumps jasmine from 4.6.0 to 5.0.1.
Release notes
Sourced from jasmine's releases.
Commits
d0b93c4
Bump version to 5.0.1b35d0c8
Depend on main branch of core7214425
Fixed state leak between multiple Jasmine instances run consecutively51b60d2
Bump version to 5.0.004c4bfe
Fixed handling of special Glob syntax in project base dirse7f5fbd
Bump version to 5.0.0-beta.09118835
Parallel: Removed redundant cluster disconnect447408e
Parallel: Report unhandled exceptions/rejections between spec filesfd6381a
Updated to Glob 100fc3a2d
Parallel: take care of pending specsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)