search

microsoft / featuretimeline

VSTS extension for managing and planning features
https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension#overview
MIT License
88 stars 45 forks source link

Bump jszip and tfx-cli #352

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps jszip and tfx-cli. These dependencies needed to be updated together. Updates jszip from 3.1.5 to 3.10.1

Changelog

Sourced from jszip's changelog.

v3.10.1 2022-08-02

  • Add sponsorship files.
    • If you appreciate the time spent maintaining JSZip then I would really appreciate your sponsorship.
  • Consolidate metadata types and expose OnUpdateCallback #851 and #852
  • use const instead var in example from README.markdown #828
  • Switch manual download link to HTTPS #839

Internals:

  • Replace jshint with eslint #842
  • Add performance tests #834

v3.10.0 2022-05-20

  • Change setimmediate dependency to more efficient one. Fixes Stuk/jszip#617 (see #829)
  • Update types of currentFile metadata to include null (see #826)

v3.9.1 2022-04-06

  • Fix recursive definition of InputFileFormat introduced in 3.9.0.

v3.9.0 2022-04-04

  • Update types JSZip#loadAsync to accept a promise for data, and remove arguments from new JSZip() (see #752)
  • Update types for compressionOptions to JSZipFileOptions and JSZipGeneratorOptions (see #722)
  • Add types for generateInternalStream (see #774)

v3.8.0 2022-03-30

  • Santize filenames when files are loaded with loadAsync, to avoid "zip slip" attacks. The original filename is available on each zip entry as unsafeOriginalName. See the documentation. Many thanks to McCaulay Hudson for reporting.

v3.7.1 2021-08-05

  • Fix build of dist files.
    • Note: this version ensures the changes from 3.7.0 are actually included in the dist files. Thanks to Evan W for reporting.

v3.7.0 2021-07-23

  • Fix: Use a null prototype object for this.files (see #766)
    • This change might break existing code if it uses prototype methods on the .files property of a zip object, for example zip.files.toString(). This approach is taken to prevent files in the zip overriding object methods that would exist on a normal object.

v3.6.0 2021-02-09

  • Fix: redirect main to dist on browsers (see #742)
  • Fix duplicate require DataLengthProbe, utils (see #734)
  • Fix small error in read_zip.md (see #703)

v3.5.0 2020-05-31

... (truncated)

Commits


Updates tfx-cli from 0.5.14 to 0.12.0

Release notes

Sourced from tfx-cli's releases.

TFX 0.9.2

Fix parsing of --manifest-js command line argument (#374)

TFX 0.9.1

Add feature to support more advanced manifest specifications (#342)

TFX 0.9.0

Remove support for publisher creation from TFX. The API backing this functionality is being removed.

TFX 0.7.11

Restores missing error-handling code in the tfx login command.

Gets rid of the login error: TypeError: Cannot read property 'success' of undefined

TFX 0.7.9

  • Add default contentType for .html files
  • Fix default categories for tfx extension init. It is now an array of every possible category. End users can trim as needed.

Support "JSON 5" with --json5 flag.

No release notes provided.

TFX 0.7.6

Mostly dependency updates to resolve known security issues.

TFX 0.7.3

Updates REST API and fixes a few issues:

  • Validation for "public" in manifest
  • Fix tfx extension install issues
  • Avoid connecting to the internet when running --help

Remove category validation for extensions.

Now we just require that you have at least 1 category, but we don't pre-validate that the category values are valid. This check will still be done on the server.

Other minor fixes, including changing branding from VSTS to Azure DevOps.

Fixes #285

No release notes provided.

0.6.0

Removed old method of installing extensions (providing account names). Now you must use tfx extension install with 1 service url, which points to a single account.

Commits
Maintainer changes

This version was pushed to npm by martinmrazik, a new releaser for tfx-cli 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/featuretimeline/network/alerts).
dependabot[bot] commented 2 years ago

Looks like these dependencies are up-to-date now, so this is no longer needed.