Bug with backporting of minor version updates to outdated versions

Forge
1

Recently we followed the backporting documentation by atlassian (https://developer.atlassian.com/platform/forge/cli-reference/deploy/#backporting) to release updates to outdated versions in order to get rid of invocation errors. At the same time, we also added a nice banner to inform our customers to update.

Imagine our surprise when we then got a support ticket “We see the banner, but no version which is more recent”. It turns out that a fresh install of our app installs the latest released version, so in this instance our backported release of an outdated version!

So we are now releasing another version on top (with the hope that this will fix it), but this was definitely a surprise to us!

20 Likes
2

@AdamMoore :open_mouth:

3 Likes
3

Nice! That was a known issue with Marketplace for Data Center releases. Good to see Atlassian is keeping the tradition alive. @marton.kelemen

6 Likes
4

Did you deploy a git hash with its parent being your last (backport) major version git hash? I’m curious if this would work? I’m looking into backporting a fix to a version before a major version upgrade which introduces app:licensing:enabled :innocent:

5

Pretty much. Each time we release a new forge version, we label it in our git commit history with the date, which made finding the right commit quite simple.

We then did the changes we wanted to, and then released a backported version using

forge deploy --major-version [version] --verbose -e production

This is documented here: https://developer.atlassian.com/platform/forge/cli-reference/deploy/#backporting

However, right after you have done this, you should release an update to your latest major version again - otherwise your backported version is now your most recent version. :melting_face:

6

Can someone from Atlassian comment on this? If new installs aren’t using the latest version (as per semver) then that is pretty wild/bad.

7

When we asked this in a support ticket, we were told ‘this behaviour is expected, Document describes this behavior.’. So @istvanverhas is absolutely right… traditions are kept alive apparantly.