runner
semver
Our great sponsors
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.
runner
-
Why the fuck are we templating YAML? (2019)
In the case of GitHub Actions, it's made more painful by the lack of support for YAML anchors, which provide a bare minimum of composability.
https://github.com/actions/runner/issues/1182
- please dont state this as a "workaround". your version simply "pretends" it is a tty when infact it is not an actual tty
-
PySide vs. .NET WinForms for a Desktop GUI App in 2023?
Even if you donβt pick Avalonia, their notes for Mac distribution look useful:
https://docs.avaloniaui.net/docs/distribution-publishing/mac...
For example, the GitHub actions runner itself is a modern .NET core project with CI except for .app packaging.
https://github.com/actions/runner/tree/main/.github/workflow...
-
GitHub Actions Are a Problem
This probably answers your question:
https://github.com/actions/runner/blob/a4c57f27477077e57545a...
-
DevOps CI/CD Quick Start Guide with GitHub Actions π οΈπβ‘οΈ
$ mkdir actions-runner && cd actions-runner $ curl -o actions-runner-osx-arm64-2.311.0.tar.gz -L https://github.com/actions/runner/releases/download/v2.311.0/actions-runner-osx-arm64-2.311.0.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 98.1M 100 98.1M 0 0 20.0M 0 0:00:04 0:00:04 --:--:-- 23.5M $ echo "fa2f107dbce709807bae014fb3121f5dbe106211b6bbe3484c41e3b30828d6b2 actions-runner-osx-arm64-2.311.0.tar.gz" | shasum -a 256 -c actions-runner-osx-arm64-2.311.0.tar.gz: OK $ tar xzf ./actions-runner-osx-arm64-2.311.0.tar.gz β― ./config.sh --url https://github.com/dpills/devops-quick-start-guide --token AGDCRGCMZWN34QIVISIO5XXXXXX -------------------------------------------------------------------------------- | ____ _ _ _ _ _ _ _ _ | | / ___(_) |_| | | |_ _| |__ / \ ___| |_(_) ___ _ __ ___ | | | | _| | __| |_| | | | | '_ \ / _ \ / __| __| |/ _ \| '_ \/ __| | | | |_| | | |_| _ | |_| | |_) | / ___ \ (__| |_| | (_) | | | \__ \ | | \____|_|\__|_| |_|\__,_|_.__/ /_/ \_\___|\__|_|\___/|_| |_|___/ | | | | Self-hosted runner registration | | | -------------------------------------------------------------------------------- # Authentication β Connected to GitHub # Runner Registration Enter the name of the runner group to add this runner to: [press Enter for Default] Enter the name of runner: [press Enter for dpills-mac] This runner will have the following labels: 'self-hosted', 'macOS', 'ARM64' Enter any additional labels (ex. label-1,label-2): [press Enter to skip] β Runner successfully added β Runner connection is good # Runner settings Enter name of work folder: [press Enter for _work] β Settings Saved. β― ./run.sh β Connected to GitHub Current runner version: '2.311.0' 2023-10-27 13:32:16Z: Listening for Jobs
-
Automate Flutter app delivery to AppCenter with GitHub Actions
A runner is where your action's jobs will be run. It can be a hosted virtual environment, or you can self-host a runner in your machine.
- GitHub Actions Frequently Failing
- Runners fail to set up job with tar -xzf error
-
How to deal with MSVC in DevOps
If i understand this writing correctly (https://github.com/actions/runner/issues/904), running Windows containers in a windows-latest GH Actions host is not possible. While using a self-hosted runner on a Windows server might be an option, this is not what I want since it is a package repo for a well-known open source project, think of the package repo part as a mini-Conan. I wouldn't know who would want to host that. In the best case we would stay with just GH Actions to keep everything confined in one space :)
-
Why is GitHub Actions installing Go 1.2 when I specify Go 1.20?
Shameless plug for cuelang, which, among many other things, avoid this problem:
https://cuelang.org
It's not a new issue, the Python community had exactly the same surprise with 3.10: https://github.com/actions/runner/issues/1989
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?
act - Run your GitHub Actions locally π
react-native - A framework for building native applications using React
azure-pipelines-agent - Azure Pipelines Agent π
semantic-release - :package::rocket: Fully automated version management and package publishing
virtual-environments - GitHub Actions runner images [Moved to: https://github.com/actions/runner-images]
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
github-act-runner - act as self-hosted runner
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
mockoon - Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
helmfile - Deploy Kubernetes Helm Charts
docker-github-runner-linux - Repository for building a self hosted GitHub runner as a ubuntu linux container
Poetry - Python packaging and dependency management made easy