Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Major version tag v2 not updated after v2.1.4 release

See original GitHub issue

We just got an update PR from dependabot which wanted to update v2 to v2.1.4, which is why I saw that v2 still points at v2.1.3. Just wanted to inform you that this might have slipped after the release.

Issue Analytics

State:
Created 3 years ago
Reactions:8
Comments:5 (3 by maintainers)

Top GitHub Comments

4reactions

dhadkacommented, Apr 12, 2021

Issue with https://github.com/actions/cache/issues/527 is resolved and @v2 is updated to the latest release @v2.1.5. Closing.

0reactions

konradpabjancommented, Apr 8, 2021

Still not pointing to v2, but small update regarding possible resolution: https://github.com/actions/cache/issues/527#issuecomment-815905807

Top Results From Across the Web

Is it possible to update major (and possibly minor) versions ...

e.g. when releasing v2.1.5 , it should move the existing v2 version from v2.1.4 to v2.1.5 . This appears to be a ...

Major Version Numbers are Not Sacred : r/programming - Reddit

In the article it says they are bumping it to v2 after just 1 month. So I guess they think it's fine to...

Introduction to Semantic Versioning | Pluralsight

This guide provides a high-level overview of semantic versioning, including how developers can tag releases in Git using semantic versioning ...

Versions and constraints - Composer

If other dependencies require a different version, the solver will ultimately fail and abort any install or update procedures. Example: 1.0.2. Version Range#....

Semantic Versioning 2.0.0 | Semantic Versioning

Once a versioned package has been released, the contents of that version MUST NOT be modified. Any modifications MUST be released as a...