Backport #149 to v3.9.x and/or v3.10.x

Open
#151 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend, release

Research direction

Start by reading issue #149 and checking the v3.9.x and v3.10.x branches to understand the security fix and whether it applies cleanly. Done means the fix is backported to the requested branch or branches and a new package is released to npmjs.

Written by the indexing model from the issue text.

Description

Would it be possible to backport #149 to v3.9.x and/or v3.10.x and release a new package to npmjs?

This is quite an important fix as it addresses a security vulnerability. Migrating to v4.0.0 is a bigger effort that we cannot really do in the short-term.

Thanks

Dominant language
JavaScript
Stars
72
Forks
42
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/tilelive-vector

All issues in mapbox/tilelive-vector

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.