chore: reset release v7 workflow and set tag "latest-v7" to all publishable package.json files

[oliverschuerch]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 46d4ee4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[swisspost-bot]

Related Previews

• https://preview-3525--swisspost-web-frontend.netlify.app
• https://preview-3525--design-system-version-7.netlify.app

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[gfellerph]

@oliverschuerch, the styles v7 are currently published under 7.4.2. If we release v7 with a tag, say @swisspost/[email protected]@latest-v7. Will somebody installing with npm i @swisspost/design-system-styles@7 get 7.4.2 or 7.4.3@latest-v7?

What happens on npm install when the styles are installed as { "@swisspost/design-system-styles": "^7.4.2" }? Do they get 7.4.3@latest-v7?

Maybe we should do some testing before implementing this.

[oliverschuerch]

@oliverschuerch, the styles v7 are currently published under 7.4.2. If we release v7 with a tag, say @swisspost/[email protected]@latest-v7. Will somebody installing with npm i @swisspost/design-system-styles@7 get 7.4.2 or 7.4.3@latest-v7?

What happens on npm install when the styles are installed as { "@swisspost/design-system-styles": "^7.4.2" }? Do they get 7.4.3@latest-v7?

Maybe we should do some testing before implementing this.

As far as I know:

• A taged version can always be installed without the tag, by just using a semver (like @7, @7.4, etc.).
• A tag set on a specific semver is always optional to use.
• A tag is unic, which means, you will never end up having to semvers using the same tag.

So:

• If you run npm i package-name@7, you will always get the latest version with the major version 7.
• You could also use npm i package-name@latest-v7, but no one will probably ever do that.
• If you run npm i package-name@latest you will always get the version which contains this tag.

I don't think this should be a problem. But we can for sure test it ;)

[gfellerph]

@oliverschuerch confirmed the behavior you described with an internal test. Tagged packages installed with in-the-middle-versions will install according to their version disregarding the tag and will not override the higher versioned latest tag.