actions-workflow-samples
semver
Our great sponsors
actions-workflow-samples | semver | |
---|---|---|
11 | 720 | |
427 | 7,020 | |
2.1% | 1.3% | |
5.8 | 2.3 | |
28 days ago | 3 months ago | |
Pug | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
actions-workflow-samples
- How best should I handle `$env/static/*` in Github Actions?
-
Github Actions for multi-tenant/subscription deployments
GitHub Actions for Azure (official examples): https://github.com/Azure/actions-workflow-samples
-
Website... Unchained
appcontent.yml - Used to deploy my app content to the Azure App Service. Using this sample provided by Microsoft, with very minor modifications.
-
What do you need in a docker-container in order to be able to publish a npm package through a GitHub action?
It's using GitHub Secrets. This guide helps: https://github.com/Azure/actions-workflow-samples/blob/master/assets/create-secrets-for-GitHub-workflows.md
-
Next.js visual regression testing made easy
For this exercise we need a personal access token from github. To ensure that the action has access to the GitHub token which you, by the way, should never expose to the public - we will place it in the secrets of the repo.
-
How to make an npm package with an automated workflow
First we'll need to make some repo secrets. Here's a nice guide from Azure explaining how to do just that. It isn't difficult at all.
-
CI/CD for WordPress on Azure with GitHub Actions
Add Actions secrets for the FTPS credentials. In our example the secret names are WP_USER and WP_PASSWORD.
-
Wagtail hosting options?
Yep. For the projects I’ve worked on, the Azure Functions for scheduling were in their own `functions` folder at the root of the repository. Upon successful deployment of the main app, we’d then deploy the functions. Aside from that deployment happening after the main app’s, we use the same deployment configuration as the official example for GitHub Actions with Python functions: https://github.com/Azure/actions-workflow-samples/blob/master/FunctionApp/linux-python-functionapp-on-azure.yml.
-
How to setup CI/CD for org-based development?
We have 1 user that we use for deployment. We keep the username and password of this user in a Secret (all platforms support some form of secrets, here is some docs on Github Actions specifically).
-
Say Hello to the Kyma Update Twitter Bot via Azure Durable Functions
I followed the official documentation (Link) and used the pre-defined template and it worked out of the box.
semver
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
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.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…
-
Testing Our Tasks
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?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
-
Semver 2.0.0 Released
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
-
First purchase advice
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.)
-
fkYAML v0.3.0: Support non-string-scalar nodes as mapping keys
If you're using semver, read the spec it's not overly long or hard to understand.
-
Immich will have breaking changes (again) in the next release
Semantic versioning actually has a clear rule about this:
What are some alternatives?
azure-docs - Open source documentation of Microsoft Azure
react-native - A framework for building native applications using React
twitter-lite - A tiny, full-featured, flexible client / server library for the Twitter API
semantic-release - :package::rocket: Fully automated version management and package publishing
Actions - ⚙️ Supercharge your shortcuts
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
kyma-updates-twitter-bot - Twitter Bot for Updatees in Kyma (and releated repos)
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
azure-storage-node - Microsoft Azure Storage SDK for Node.js
helmfile - Deploy Kubernetes Helm Charts
twurl - OAuth-enabled curl for the Twitter API
Poetry - Python packaging and dependency management made easy