spellcheck-github-actions
semver
spellcheck-github-actions | semver | |
---|---|---|
23 | 727 | |
130 | 7,052 | |
- | 1.0% | |
6.5 | 0.6 | |
9 days ago | about 1 month ago | |
Shell | ||
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.
spellcheck-github-actions
-
Release 0.36.0 of Spellcheck (GitHub) Action - another maintenance release
Docker image updated to Python 3.12.1 slim via PR #177 from Dependabot. Release notes for Python 3.12.1
-
Release 0.35.0 of Spellcheck (GitHub) Action - another maintenance release
Today I have released version 0.35.0 of the GitHub Action for doing spelling checking of your documentation etc. for which I am the current maintainer.
-
Forks of Forks
GitHub Actions are convenience for packaging tooling for execution on the GitHub platform or using a local runner etc. As you can see on the GitHub Marketplace this mean that a lot of actions are wrapping of common and useful tools to adapt to the GitHub toolbox and toolchain. The same goes for GitHub Spellcheck Actions, it is an implementation based on PySpelling a nifty tool to do spelling checks on Python, Markdown, Text files etc.
-
Release 0.29.0 of Spellcheck (GitHub) Action - a maintenance release
The release is just a maintenance release with no significant changes, one could ask why I would even write about a maintenance release and I can see that I did not write about when I released 0.28.0, which was also just a maintenance release.
-
Release 0.27.0 of Spellcheck (GitHub) Action - a feature release with improved support for PySpelling default configuration
Finally I got around to pushing release 0.27.0 of the GitHub Spellcheck Action, it has been in my TODO pipeline for way too long.
-
Release 0.26.0 of Spellcheck (GitHub) Action - a maintenance updating core component
The 0.15.0 and 0.16.0 versions are announced to be sunsetted.
-
Release 0.25.0 of Spellcheck (GitHub) Action - a maintenance release including a security fix
lxml requirement bumped from version 4.6.5 to 4.9.1 addressing a security issue SNYK-PYTHON-LXML-2940874 / CVE-2022-2309 / CWE-476 via PR #104 from @snyk-bot
-
Release 0.24.0 of Spellcheck (GitHub) Action - a feature release introducing optional artifacts
Feedback and questions about this new feature is of course welcome, here as well as in the Discussions section in the GitHub repository.
-
Proposal for a Sunset Policy for a GitHub Action
I am the current maintainer of a GitHub Action for checking spelling in files in a GitHub repository. The action "GitHub Spellcheck Action" (rojopolis/spellcheck-github-actions) has grown in popularity and is used in several GitHub repositories, meaning that changes to the software and it's availability has become significant factors in it's life cycle. At the same time, it is based on open and free infrastructure and maintenance, so I decided it was time to introduce a sunset policy.
-
Release 0.23.1 of Spellcheck (GitHub) Action - a bug fix release
Addressing issue #84 via PR #90 from @jonasbn. With the introduction of use of optional quotes, do note the limitations outlined in the documentation - thanks to @xsaero00 for the bug report
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?
pyspelling - Spell checker automation tool
react-native - A framework for building native applications using React
Python-Markdown - A Python implementation of John Gruber’s Markdown with Extension support.
semantic-release - :package::rocket: Fully automated version management and package publishing
xmllint-problem-matcher - Shows xmllint errors in GitHub Actions as annotation with file and code line
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
perl-workflow - Workflow - simple, flexible system to implement workflows/state machines
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
github-pages-javascript-prototype - Experimenting with GitHub pages and JavaScript and local data
helmfile - Deploy Kubernetes Helm Charts
spellcheck-github-actions-example - Example for spellcheck-github-actions
Poetry - Python packaging and dependency management made easy