nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GreenHopper plugin indicates an unreleased version 6.0.1 after Jira 5.1.2 and plugins ugrades

Jari Kokkonen

Hi,

After upgrading to Jira 5.1.2#773 and performing the suggested GreenHopper plugin upgrade, the Plugins -> User Installed Plugins -> GreenHopper indicates that I am running an unreleased version 6.0.1 of the plugin (see attached screenshot), which cannot be true - can it?

BR,

Jari

Accepted answers

Ruchi Tandon

This is actually a bug in UPM : https://ecosystem.atlassian.net/browse/UPM-2484.

The main problem is that if there are draft versions of plugins, then UPM recognizes them as valid updates while they are not.

All comments

Jari Kokkonen

Andrew Morin

I get something a little different..so am I running 5.10.6 but have 6.0.1 installed??

unknown

I have the same issue, but with jira version 5.1.1

Ruchi Tandon

I was able to reproduce the problem on a clean install. I have reported the bug here : https://jira.atlassian.com/browse/GHS-5618.

Norman Abramovitz

This is not so uncommon. I have noticed this type of issue before because there are multiple places that need to updated but the first thing is the code needs to updated before the other places are updated. So you end up with a newer version that may not be marked correctly. For example, the UPM plugin was not valid for 5.1.1 by the plugin update screen.

Ruchi Tandon

This is actually a bug in UPM : https://ecosystem.atlassian.net/browse/UPM-2484.

The main problem is that if there are draft versions of plugins, then UPM recognizes them as valid updates while they are not.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

app