Skip to content
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

chore(deps): bump the pip group across 2 directories with 1 update #36

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 14, 2025

Bumps the pip group with 1 update in the / directory: virtualenv.
Bumps the pip group with 1 update in the /tools/tlc directory: virtualenv.

Updates virtualenv from 20.26.4 to 20.26.6

Release notes

Sourced from virtualenv's releases.

20.26.6

What's Changed

New Contributors

Full Changelog: pypa/virtualenv@20.26.5...20.26.6

20.26.5

What's Changed

Full Changelog: pypa/virtualenv@20.26.4...20.26.5

Changelog

Sourced from virtualenv's changelog.

v20.26.6 (2024-09-27)

Bugfixes - 20.26.6

- Properly quote string placeholders in activation script templates to mitigate
  potential command injection - by :user:`y5c4l3`. (:issue:`2768`)

v20.26.5 (2024-09-17)

Bugfixes - 20.26.5

  • Upgrade embedded wheels: setuptools to 75.1.0 from 74.1.2 - by :user:gaborbernat. (:issue:2765)
Commits

Updates virtualenv from 20.26.5 to 20.26.6

Release notes

Sourced from virtualenv's releases.

20.26.6

What's Changed

New Contributors

Full Changelog: pypa/virtualenv@20.26.5...20.26.6

20.26.5

What's Changed

Full Changelog: pypa/virtualenv@20.26.4...20.26.5

Changelog

Sourced from virtualenv's changelog.

v20.26.6 (2024-09-27)

Bugfixes - 20.26.6

- Properly quote string placeholders in activation script templates to mitigate
  potential command injection - by :user:`y5c4l3`. (:issue:`2768`)

v20.26.5 (2024-09-17)

Bugfixes - 20.26.5

  • Upgrade embedded wheels: setuptools to 75.1.0 from 74.1.2 - by :user:gaborbernat. (:issue:2765)
Commits

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the pip group with 1 update in the / directory: [virtualenv](https://github.com/pypa/virtualenv).
Bumps the pip group with 1 update in the /tools/tlc directory: [virtualenv](https://github.com/pypa/virtualenv).


Updates `virtualenv` from 20.26.4 to 20.26.6
- [Release notes](https://github.com/pypa/virtualenv/releases)
- [Changelog](https://github.com/pypa/virtualenv/blob/main/docs/changelog.rst)
- [Commits](pypa/virtualenv@20.26.4...20.26.6)

Updates `virtualenv` from 20.26.5 to 20.26.6
- [Release notes](https://github.com/pypa/virtualenv/releases)
- [Changelog](https://github.com/pypa/virtualenv/blob/main/docs/changelog.rst)
- [Commits](pypa/virtualenv@20.26.4...20.26.6)

---
updated-dependencies:
- dependency-name: virtualenv
  dependency-type: indirect
  dependency-group: pip
- dependency-name: virtualenv
  dependency-type: indirect
  dependency-group: pip
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jan 14, 2025
@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

3 similar comments
@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 17, 2025

Superseded by #38.

@dependabot dependabot bot closed this Jan 17, 2025
@dependabot dependabot bot deleted the dependabot/pip/pip-1cecd3b3de branch January 17, 2025 22:07
@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

1 similar comment
@openci-bot
Copy link
Collaborator

Hello @dependabot[bot]!

Thank you for your contribution to Trusted Firmware-A!

The TF-A project has now migrated to www.trustedfirmware.org. Our GitHub repo will remain accessible as a Read-Only mirror but we have changed the way we accept contributions for the project.

How do I contribute patches to TF-A?

We have a Getting started article which we hope will make everything very straightforward! And if you would like more details you can always refer to the contributing guidelines.

A quick overview:

  1. Go to review.trustedfirmware.org
  2. Register with your existing GitHub account
  3. Submit your patches!

What if I face any problems?

We have many channels through which you can contact us:

  • Our mailing lists
    You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing your patch submitted to trustedfirmware.org!

The Trusted Firmware-A team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant