Skip to content

Commit

Permalink
Bump taskcluster from 65.1.0 to 65.2.0 in /taskcluster (#9681)
Browse files Browse the repository at this point in the history
Bumps [taskcluster](https://github.com/taskcluster/taskcluster) from 65.1.0 to 65.2.0.
- [Release notes](https://github.com/taskcluster/taskcluster/releases)
- [Changelog](https://github.com/taskcluster/taskcluster/blob/main/CHANGELOG.md)
- [Commits](taskcluster/taskcluster@v65.1.0...v65.2.0)

---
updated-dependencies:
- dependency-name: taskcluster
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
  • Loading branch information
dependabot[bot] committed Jun 24, 2024
1 parent 33fd529 commit 2547860
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion taskcluster/scripts/requirements.in
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
multidict >= 5.0.0
yarl>=1.6.0
taskcluster==65.1.0
taskcluster==65.2.0
6 changes: 3 additions & 3 deletions taskcluster/scripts/requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -362,9 +362,9 @@ slugid==2.0.0 \
--hash=sha256:a950d98b72691178bdd4d6c52743c4a2aa039207cf7a97d71060a111ff9ba297 \
--hash=sha256:aec8b0e01c4ad32e38e12d609eab3ec912fd129aaf6b2ded0199b56a5f8fd67c
# via taskcluster
taskcluster==65.1.0 \
--hash=sha256:dd1e25daa6dc160b830a30482da21ad8b0b0be846df3630078c2cde7037e17a6 \
--hash=sha256:fefca91c68f096067bbeb25926e78f4c1656164423d46a71206fa0f293e365e9
taskcluster==65.2.0 \
--hash=sha256:65e3cefc7aff1745a0c4205e7e796a8c000c7cb454f1df04bf258f4355aca741 \
--hash=sha256:bf206b5d7aede0863d366bf70dcee1792e3b664f6b77d3bf91c0c0fe296f3bf0
# via -r scripts/requirements.in
taskcluster-urls==13.0.1 \
--hash=sha256:5e25e7e6818e8877178b175ff43d2e6548afad72694aa125f404a7329ece0973 \
Expand Down

0 comments on commit 2547860

Please sign in to comment.