hashicorp / hashicorp/consul

Update release process to ensure "latest" release is accurate

Open
#17,388 5 comments 0 reactions 0 assignees View on GitHub
type/ci type/enhancement
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
1d 18h
Merged PRs (30d)
39

Description

This relates to #16093 there has been a new release generated for 14.x which is marked as latest, when there is a release of 15.x that is also available which is the real latest. Please update your release process so that only releases on the newest version are marked as latest

Contributor guide

Open the contributing guide

Research direction

Review the release process and the context in issue #16093 first. Identify where releases are selected or marked as latest, then verify the process against available 14.x and 15.x releases. Done means only releases from the newest version are marked as latest.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.