You can check the source code for it here. The runner that executes GitHub Actions for us is open source. ![]() What the runner does with semantic versioning of using GitHub Actions ![]() Effectively that means that you’re saying 9.*.*. This means that you will get the latest version of 9.1 and 9.2 and 9.3 and so on. If you specify version 9, you will get the latest version of that MAYOR version. The same setup goes for the MINOR version. If version 9.2.0 is released, your package manager will not download that version, because it does not match the MAYOR.MINOR version you specified. If version 9.1.4 is released, your package manager will download that version. If version 9.1.3 is the current latest PATCH version, your package manager will download that version. Effectively that means that you’re saying 9.1.*. You can just specify the MAYOR.MINOR version and you will get the latest version of that version. This is very useful when you want to use the latest version of a library, but you don’t want to have to update your code every time a new version is released. This means you will get the latest version of 9.1 that is available. Following SemVer this means you want to use any version that matches the 9.1 MAYOR.MINOR version. You can be very specific and say you want to use version 9.1.4, but also be less specific and say you want to use version 9.1. The goal of using SemVer is that you can then specify what you as a user of a library want to use. Optionally you can use any suffix label you want to indicate special versions like alpha, beta, release candidate, etc: PATCH version when you make backwards compatible bug fixes.MINOR version when you add functionality in a backwards compatible manner.MAJOR version when you make incompatible API changes.Given a version number you increment the: Semantic versioning (SemVer) is an industry wide standard of giving meaning to the version number. ![]() When using GitHub Actions, the default is to use the Semantic Versions for which the actions where released. It’s more secure to use a SHA hash instead of a tag: read more info here.If the maintainer does not actually release, it’s not visible The marketplace shows releases, not tags.Even GitHub does not update (or create) all SemVer versions, so is not necessarily the latest thing for v3!.The runner just downloads what you specified, by getting it from the tag.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |