[CI] CI does not publish snapshots of release branches

[SevaZhukov]

https://mapbox.atlassian.net/browse/NAVAND-501

Run release-snapshot workflow on publish-snapshot label

[github-actions]

Changelog

Features

Bug fixes and improvements

• Improved NavigationView camera behavior to go back into overview state if routes change during route preview state. #6840

Known issues ⚠️

Other changes

Android Auto Changelog

Features

Bug fixes and improvements

[codecov]

Codecov Report

Merging #6843 (04768c4) into main (1098030) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #6843   +/-   ##
=========================================
  Coverage     72.64%   72.64%           
  Complexity     5564     5564           
=========================================
  Files           781      781           
  Lines         30116    30116           
  Branches       3561     3561           
=========================================
  Hits          21878    21878           
  Misses         6810     6810           
  Partials       1428     1428           

[RingerJK]

It works 👍

Seems that if names somehow are the same the newest snapshot substitute the legacy one.
We must be careful and provide snapshots with unique names. Seems if a name contains a number of jira's ticket it should be enough.

[dzinad]

Seems that if names somehow are the same the newest snapshot substitute the legacy one.
We must be careful and provide snapshots with unique names. Seems if a name contains a number of jira's ticket it should be enough.

I think it's how it's supposed to be for snapshots. You may want to rewrite them. For example, if you are testing something from a branch, for the second, third and so forth iterations you wouldn't want to think of new version names.

[RingerJK]

I think it's how it's supposed to be for snapshots. You may want to rewrite them. For example, if you are testing something from a branch, for the second, third and so forth iterations you wouldn't want to think of new version names.

I'm on the same page, just worrying if coincidentally names of the branch match, and it will lead to version substituting of a snapshot. Let's not worry about it for now 👍