Skip to content

Bump parse-path and lerna #5

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump parse-path and lerna #5

wants to merge 1 commit into from

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Jun 22, 2023

Bumps parse-path to 7.0.0 and updates ancestor dependency lerna. These dependencies need to be updated together.

Updates parse-path from 4.0.4 to 7.0.0

Release notes

Sourced from parse-path's releases.

7.0.0

Add the parse_failed property — whether the input was parsed successfully or not.

6.0.0

parse-path 6.0.0

Breaking changes

  • The resource property will not contain the port anymore. Added the host property which has the port too.

5.0.0

parse-path 5.0.0

⭐ This is a major release of parse-path! ⭐

Breaking changes

  • parse-path will not parse git@... ssh URLs anymore. Use parse-url for that.
  • If the input url has a trailing slash, the trailing slash will be added in the pathname too.
  • The port field is a string. By default empty.
  • Added the password field (default: "")
  • The resource may contain the port in it (e.g. resource: "domain.com:4200").

Features

  • Faster
  • More secure
  • Cleaner codebase

Any questions, suggestions, contributions are always welcome! 😊

Commits

Updates lerna from 4.0.0 to 7.0.2

Release notes

Sourced from lerna's releases.

7.0.2

7.0.2 (2023-06-15)

Bug Fixes

  • publish: revert auto-copying of assets to custom contents/directory (#3732) (70d4438)

7.0.1

7.0.1 (2023-06-13)

Bug Fixes

  • core: reset nx daemon after command finishes (#3726) (c0de66a)

7.0.0

7.0.0 (2023-06-08)

BREAKING CHANGES

After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.

As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.

  • legacy package management commands have been removed

We no longer include the bootstrap, add, and link commands by default. We strongly recommend using your package manager (npm, yarn, pnpm) for package management related concerns such as installing and linking dependencies.

There will not be any active work done on these commands and you should look to migrate as soon as possible.

For full context how why we made this change and how you can migrate your projects, please read our detailed guide here: https://lerna.js.org/docs/legacy-package-management

  • Workspaces are used by default and useWorkspaces has been removed

We now use your package manager's workspaces configuration by default in order to resolve packages for lerna to operate on. If you wish to customize the packages that lerna will operate on, you can still use a packages property in your lerna.json just as you did before, but there is no longer any need for a useWorkspaces flag. If the packages property is present, lerna will use that, otherwise it will try and read your workspaces configuration.

Running lerna repair will automatically remove useWorkspaces from your lerna.json for you.

NOTE: If you are using pnpm as your package manager, it is important to set "npmClient": "pnpm" in your lerna.json so that lerna knows to look for a pnpm-workspaces.yaml file and not just check your root package.json.

  • lerna init can no longer be run on an existing lerna repo

It was a confusing behavior that lerna init could be run on an existing lerna repo and would attempt to coerce its setup to something closer to a fresh repo, so we have removed this behavior and lerna will hard error if it detects the directory is already initialized.

You can run lerna repair at any time to update your configuration to the latest and greatest.

  • long deprecated options have been removed

The following options (on the left of the => in each case) have been deprecated for many years (since before we took over stewardship of the project) and have finally been removed. If you are using them in your lerna.json all you need to do is run lerna repair and it will automatically migrate you to their modern equivalent. If you are passing them in on the command line, you will need to update your usage as follows:

... (truncated)

Changelog

Sourced from lerna's changelog.

7.0.2 (2023-06-15)

Note: Version bump only for package lerna

7.0.1 (2023-06-13)

Note: Version bump only for package lerna

7.0.0 (2023-06-08)

Bug Fixes

Features

  • add migration for adding $schema, increase some strictness (73ceac3)

7.0.0-alpha.8 (2023-06-07)

Bug Fixes

Features

  • add migration for adding $schema, increase some strictness (73ceac3)

7.0.0-alpha.7 (2023-06-05)

Bug Fixes

Features

  • add migration for adding $schema, increase some strictness (73ceac3)

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by jameshenry, a new releaser for lerna since your current version.


Dependabot 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump parse-path and lerna
33778c5 
Bumps [parse-path](https://github.com/IonicaBizau/parse-path) to 7.0.0 and updates ancestor dependency [lerna](https://github.com/lerna/lerna/tree/HEAD/packages/lerna). These dependencies need to be updated together.


Updates `parse-path` from 4.0.4 to 7.0.0
- [Release notes](https://github.com/IonicaBizau/parse-path/releases)
- [Commits](IonicaBizau/parse-path@4.0.4...7.0.0)

Updates `lerna` from 4.0.0 to 7.0.2
- [Release notes](https://github.com/lerna/lerna/releases)
- [Changelog](https://github.com/lerna/lerna/blob/main/packages/lerna/CHANGELOG.md)
- [Commits](https://github.com/lerna/lerna/commits/7.0.2/packages/lerna)

---
updated-dependencies:
- dependency-name: parse-path
  dependency-type: indirect
- dependency-name: lerna
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 22, 2023
gonzalojaubert pushed a commit that referenced this pull request Sep 21, 2023
Merge pull request #5 from Optum/multipart
b8a08b8 
Multipart form-data requests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants