terraform-provider-azuread VS semver

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

It can be for anything. Here is the provider for Azure Active Directory. It looks like it has over a million downloads this week alone so someone is using it..

Since the provider doesnt currently support licensing on [users directly](https://github.com/hashicorp/terraform-provider-azuread/issues/745) i think the only other option is to create a group that maintains specific licenses for user-members... however, that seems to be pay-walled behind Business Premium or azure ad p1

Not officially supported yet: https://github.com/hashicorp/terraform-provider-azuread/issues/68

The support for privileged identity management in Terraform is very limited. One open issue that tracks it is https://github.com/hashicorp/terraform-provider-azuread/issues/547

Source: https://github.com/hashicorp/terraform-provider-azuread/blob/main/internal/services/directoryroles/directory_role_resource.go

I haven't particularly worked with this, but if you're looking for things to see before doing, I would recommend looking at the examples provided by Microsoft: https://docs.microsoft.com/en-us/azure/developer/terraform/ and read through the provider documentation to see the individual pieces: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: