news-for-maintainers
semver
news-for-maintainers | semver | |
---|---|---|
4 | 727 | |
24 | 7,044 | |
- | 0.9% | |
1.3 | 0.6 | |
about 1 year ago | 22 days ago | |
- | - |
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.
news-for-maintainers
-
The Bullhorn #83 (Ansible Newsletter)
If you are using GHA to run tests on collections, you might have noticed strange failures when using ansible-test's --docker option when using ubuntu-latest. Read more about this and how to fix this in this issue.
-
The Bullhorn #52 (Ansible Newsletter)
In ansible/ansible, the stable-2.13 branch has been created (more infos), and the version of the devel branch has been bumped to 2.14.0.dev0 (more infos).
-
The Bullhorn #44 (Ansible Newsletter - now weekly!)
If you want to discuss this, we welcome feedback in ansible-collections/news-for-maintainers/discussions/4.
-
The Bullhorn #43 (Ansible Newsletter)
In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that has just been closed. To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page. If you do not want to get notifications about related discussions, please subscribe only to Issues. Please read the brief guidelines on how the repository should be used. Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
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
What are some alternatives?
community.aws - Ansible Collection for Community AWS
react-native - A framework for building native applications using React
ansible.utils - A collection of ansible utilities for the content creator.
semantic-release - :package::rocket: Fully automated version management and package publishing
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
community.google
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
ara - ARA Records Ansible and makes it easier to understand and troubleshoot.
helmfile - Deploy Kubernetes Helm Charts
community-docs - docs.ansible.com/community
Poetry - Python packaging and dependency management made easy