Carthage/Carthage

The check for new Carthage release should ignore draft releases

Open

#1,791 opened on Feb 27, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Swift (1,544 forks)batch import
bughelp wanted

Repository metrics

Stars
 (15,179 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

*** Please update to the latest Carthage version: 0.20.0. You currently are on 0.19.1

This shouldn't happen until the release has been marked as a non-draft.

Contributor guide

Research direction
Find where Carthage checks for the latest release version and add a condition to skip draft releases.
Tech stack
swift
Domain
backendcli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitSwift
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65