Relase github-release-tools

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
release

Research direction

Start by reviewing the repository's release scripts and the existing process for publishing GitHub and NPM versions. Identify the latest version containing the resolved bugs, then coordinate both releases before the next GL JS release. Done means the GitHub and NPM versions are publicly released.

Written by the indexing model from the issue text.

Description

Context

The last release was almost two years ago, and there have been several important bugs resolved since then. Using the latest version currently requires a download and NPM link.

Acceptance Criteria

Release Github and NPM versions before the next GL JS release.

Dominant language
JavaScript
Stars
16
Forks
5
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/github-release-tools

All issues in mapbox/github-release-tools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.