Carthage/Carthage

The check for new Carthage release should ignore draft releases

Open

#1791 opened on Feb 27, 2017

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

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

Tech stack
swift
Domain
clireleasetooling
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
SwiftGitHub APIRelease management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the source code responsible for fetching release information from GitHub. Look for where releases are queried and ensure that the API call includes a filter to exclude draft releases. Review the existing comments in the issue for any suggested approaches. The fix should be localized to that file.