DEV Community: GitHub

Speed Up Your CI/CD: ARM 64 Runners for GitHub Actions

Andrea Liliana Griffiths — Thu, 15 May 2025 12:24:18 +0000

Hey dev.to community! 👋🏽

I'm Andrea Griffiths, Senior Developer Advocate at GitHub, and I'm excited to share our latest GitHub Checkout episode: Build & deploy across multi-architecture FASTER with ARM 64 Runners.

Why This Matters

If you're using GitHub Actions for your CI/CD pipelines, this is a massive improvement for handling multi-architecture development. GitHub has expanded runner infrastructure to include Arm64 support, enabling faster, more efficient workflows across diverse architectures.

This is especially crucial if you're building applications for:

Cloud environments
Edge computing
IoT devices
Machine learning workloads

What You'll Learn

In this GitHub Checkout video featuring Product Manager Larissa Fortuna, you'll discover:

How Arm64 runners for GitHub Actions are transforming development workflows
The significant speed improvements compared to emulation (some customers reduced build times from 3 hours to just 20 minutes!)
How to create multi-architecture Docker images efficiently
Ways to reduce carbon emissions (Arm processors use 30-40% less power in data centers)
Available tools to measure the carbon footprint of your Actions runs

The best part? Arm64 runners are free for public repositories with unlimited minutes (only concurrent job limits apply)!

Resources Shared in the Video

For those looking to get started:

MULTI-ARCHITECTURE BUILDS

Docker docs: https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners
Public github repo: https://github.com/gartnera/actions-arm64-native-example

COMMUNITY DISCUSSION

Linux discussion: https://github.com/orgs/community/discussions/148648
Windows discussion: https://github.com/orgs/community/discussions/155713
Eco-ci tool for estimating carbon emissions: https://github.com/green-coding-solutions/eco-ci-energy-estimation

Join the Conversation

After watching the video, I'd love to hear your thoughts:

Are you already using Arm64 runners in your CI/CD pipelines?
What kind of performance improvements have you seen?
How are you handling multi-architecture deployments for your projects?

Check out the episode here: https://youtu.be/xHJ8som-D6Y

Looking forward to your comments!

Showcase your open source project at SCALE 🐧 Pasadena, CA · March 6-9, 2025

Lee Reilly — Fri, 24 Jan 2025 17:51:20 +0000

Hi everyone! 👋

We're thrilled to invite open source maintainers to an amazing opportunity: showcasing your projects in the GitHub Booth at the 22nd annual SCALE (Southern California Linux Expo), happening March 6-9, 2025!

SCALE is the largest community-run open-source and free software conference in North America, held at the Pasadena Convention Center. It’s the perfect place to connect with a dynamic open-source community, share your amazing work, and meet developers, enthusiasts, and industry leaders.

What’s in it for you?

🎉 A dedicated space in the GitHub Booth to spotlight your project.
🎟️ 2 complimentary passes to the conference.
💡 Access to inspiring talks and a chance to network with the open-source community.

How to apply

If you’re interested in being part of this incredible event, submit your application today. But don’t wait too long—applications close on February 7th, 2025. Questions? Email opensourcezone@github.com.

⚡ Don’t miss out on this fantastic chance to showcase your work and connect with the community. We look forward to seeing you at SCALE!

Apply Now: https://gh.io/scale22x-open-source-zone

Cheers,
Lee

PS: We did something similar in Berlin last summer and everyone had a great time (see image below). This one may be smaller in scale. Pun intended.

^{Armeria, audioserve, Carapace, Cilium, cote, DBeaver, decidim, dlthub, dstack, Homebrew, ImageGlass, Immersive Home, Infracost, ingestr, Kitspace.org, kluctl, libgit2, Nanocl, Oh My Zsh, Pact, pgroll, Step CI, Unikraft, Wolfi exhibiting at the Open Source Fair at The Merge in Berlin, July 2024.}

Release Radar · September 2024: Major updates from the open source community

Michelle Duke — Sat, 05 Oct 2024 00:49:35 +0000

We're heading into the spooky season, which means Hacktoberfest has also started. This is a month-long celebration of open source; encouraging developers to contribute to open source projects. If you're struggling to find good projects, you might find some inspiration here. There's everything from fun side hustles, to groundbreaking technology. Let's take a look at GitHub's picks for this month's Release Radar; a roundup of the open source projects that have shipped major version updates.

Redwood 8.0

If you're looking to swiftly create some React-based web applications, then Redwood is for you. It's the perfect framework if you're looking to mock up something for a hackathon, a startup, or to create a decent prototype to show off your next big idea. The latest version brings background jobs, a way for you to create and execute background jobs within your React-based app; send an email or process an image. There's now support for Docker, and updates for the latest versions of React, Prisma, Vite, and more. Check out the full release blog for all the details.

Express 5.0

More frameworks! This one is for Node.js applications, and is designed to be minimalist. There are tonnes of changes to the latest version of Express, including new document beta releases expectations, a new threat model, added CodeQL (SAST), support for Node 22, and lots more. Check out all the changes, as well as new contributors, in the Express release notes.

const express = require('express')
const app = express()

app.get('/', function (req, res) {
  res.send('Hello World')
})

app.listen(3000)

date-fns 4.0

JavaScript seems to be the flavour of the month, and here's another JavaScript project for you. date-fns provides the most comprehensive and consistent toolset for manipulating JavaScript dates in a browser & Node.js. The latest version comes ten years after the very first release. There are no breaking changes in the release, and it comes with added time zone support, meaning you can select which time zone to make calculations in. There are some changes to functional arguments and a few fixes. Read up on all the changes in the release notes.

import { addDays, startOfDay } from "date-fns";
import { tz } from "@date-fns/tz";

startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
//=> "2024-09-16T00:00:00.000+08:00"

Prefect 3.0

Let's switch gears from JavaScript to Python. Prefect is a workflow orchestration framework for building data pipelines in Python. Workflow activity is tracked and can be monitored with a self-hosted server, or managed dashboard. The latest release is now 10x faster, event-driven, and comes with a robust API. These new pre-built event-driven workflows are available in Prefect-Open-Source. Your data can now tell your workflows when they are ready to be processed. Check out all the few features and updates in the Prefect blog post.

from prefect.automations import Automation
from prefect.events.actions import PauseDeployment
from prefect.events.schemas.automations import EventTrigger

my_automation = Automation(
    name="Pause critical workflow",
    trigger=EventTrigger(
        expect={"prefect.flow-run.Failed"},
        match={"prefect.resource.id": ["prefect.flow-run.*"]},
        match_related={
            "prefect.resource.role": "flow",
            "prefect.resource.name": [
                "critical_workflow",
            ],
        },
    ),
    actions=[PauseDeployment(source="inferred")],
)

my_automation.create()

PacketFence 14.0

Looking for a network access control (NAC) solution? Then look no further than PacketFence. This solution includes a captive-portal for registration and remediation, centralised wired, wireless and VPN management, industry-leading BYOD capabilities, 802.1X and RBAC support, integrated network anomaly detection with layer-2 isolation of problematic devices. PacketFence version 14 brings support for Debian 12 and OSQuery, as well as some neat enhancements including Firewall SSO clustering load-balancing, and cluster support for domain.conf.

Kingfisher 8.0

I'm not much of an Apple user, but Swift developers will love this. Kingfisher is a library for downloading and caching images on the web. It includes asynchronous image downloading and caching, multi-layer hybrid cache for both memory and disk, and some useful image processors and filters. The latest version includes support for Swift Concurrency, compatibility with Swift 6, and backward language compatibility. Check out all the changes, including some breaking changes in the release notes.

onevcat / Kingfisher

A lightweight, pure-Swift library for downloading and caching images from the web.

Kingfisher is a powerful, pure-Swift library for downloading and caching images from the web. It provides you a chance to use a pure-Swift way to work with remote images in your next app.

Features

Asynchronous image downloading and caching.
Loading image from either URLSession-based networking or local provided data.
Useful image processors and filters provided.
Multiple-layer hybrid cache for both memory and disk.
Fine control on cache behavior. Customizable expiration date and size limit.
Cancelable downloading and auto-reusing previous downloaded content to improve performance.
Independent components. Use the downloader, caching system, and image processors separately as you need.
Prefetching images and showing them from the cache to boost your app.
Extensions for UIImageView, NSImageView, NSButton, UIButton, NSTextAttachment, WKInterfaceImage, TVMonogramView and CPListItem to directly set an image from a URL.
Built-in transition animation when setting images.
Customizable placeholder and indicator while loading images.
Extensible…

View on GitHub

n 10.0

Short for "interactively manage Node.js versions", n helps you manage your version of Node.js without any profile setup, subshells, or API hook. The latest version is mainly due to the use of jq over node for reading package.json. n can also avoid a network lookup if either auto or engine finds a specified numeric version.

Verdaccio 6.0

Are you tired of needing an entire database just to get started? Verdaccio changes all that with an out-of-the-box database you can use for your local private npm registry. It can proxy other registers, and cache downloaded modules. The newest update drops support for Node.js 16, taking minimum support for Node.js 18.

🤗 Datasets 3.0

From Hugging Face, come 🤗 Datasets, the largest hub of ready-to-use datasets for machine learning models. The latest update comes with support for Polars functions and NumPy2. There's some deprecated code and cache changes. There's improvements to tutorial with a link for loading datasets and some fixes. Read up on all the changes, fixes, and new contributors in the 🤗 Datasets release notes.

Realm 20.0

From the team at MongoDB comes Realm, a mobile database that runs directly inside phones, tablets, or wearables. It's built for mobile, and designed for offline use. The latest release comes with built-in Swift 6 language mode, and Xcode 16 support. Some breaking changes include removal of Atlas App Services and Atlas Device Sync functionality, Strings and Data now considered different types and thus queries won't match one another, and Realms are no longer autoreleased when initialised. Dig into all the updates in the Realm changelog.

Release Radar September

Well, that’s all for this edition. Hopefully you have some ideas on projects you'd like to contribute to for Hacktoberfest. Thanks to everyone who submitted a project to be featured. We loved reading about the great things you're all working on. Whether your project is featured here or not, congratulations to everyone who shipped a new release 🎉, regardless of whether you shipped your project's first version, or you launched 20.0.

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in August. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

A checklist and guide to get your repository collaboration-ready

peckjon — Wed, 18 Sep 2024 18:44:15 +0000

Want the TL;DR, or you’ve already been using GitHub for a while? Skip to the end for a printable checklist that you can use to ensure that you’ve covered all aspects of making your repository collaboration-ready.

My daughter has a pair of pet gerbils. They’re awesome, but not the most complex creatures to care for. They need their cage cleaned occasionally, their food and water refilled, and may need a neighbor to check in on them if we’re away for a while. But someday, she may have a pet that requires more care and attention–a cat or dog perhaps, which needs to be played with and nurtured every day–so she’ll want to have a few good friends who know her pet and can be their companion whenever she’s away. And someday, she may even have a child of her own, making her connections to community and family ever more important. As the saying goes, it takes a village to raise a child.

So it goes with code projects. My colleagues and I often refer to our projects as “pets” or even “children” (sometimes jokingly, sometimes obsessively). We pour a lot of our own care and attention into them, but it can be easy to forget how important the community’s contributions can be to their success. In the world of software development, collaboration can make the difference between a brittle last-minute release and a reliable, maintainable, pain-free project. Whether you’ve been coding for a day or a decade, your colleagues are there to help strengthen your work. But they can only help if you’ve given them the tools to do so.

Your primary responsibility as the creator or maintainer of a repository is to ensure that others can appropriately use, understand, and even contribute to the project. GitHub is here to support that mission, but ensuring that a repository is collaboration-ready takes a bit more effort than using git clone. So read on to learn the settings, content, and behaviors that will help you succeed.

1. Repository settings

The settings of your repository lay the foundation for collaboration. They determine who can see and contribute to your project, how contributions are reviewed, and what happens to those contributions once they are submitted. Properly used, they can foster an environment in which contributors across the globe will find, make use of, and help build your project. In a corporate setting, they help shift developers from a siloed way of thinking and building to a “search-first, collaborate-first” mindset. This practice, known as innersourcing, reduces redundant work and accelerates the whole company.

Visibility

You’re aiming to maximize contributions and reuse, but that doesn’t always mean making your repository public, especially in a corporate setting where information privacy is a consideration. You have several options available in the “Settings” tab of your repository.

Public lets anyone in the world see and copy your code, and generally allows them to create issues or pull requests, so they can provide feedback about whether it works well, or even suggest (but not force) changes to improve it. This is generally great for personal projects containing no protected information (those tokens are all stored separately, right?) but only for certain “blessed” company projects.
Internal is a special visibility level used by GitHub Enterprise, allowing anyone inside your organization to see the repository, but nobody in the outside world. We generally suggest this as the default level for company projects that don’t have siloed sensitive information (such as customer-specific data or logic that only a specific group should know about).
Private is the most restrictive option, and can be a collaboration-killer. Use this option sparingly, and if you do, be sure to invite some collaborators.
Collaborators are specific individuals or teams you invite to be part of your project. They can be given specific roles such as “Read” (allowing them to see your otherwise private repository), “Write” (letting them directly commit or manage pull requests), “Admin”, and many others.

Protect the main branch

While you want to maximize the number of people who can see and contribute to your project, you still need to ensure that their contributions are properly reviewed, both by your core team members and by automation. In most cases, you’ll want to create a repository rule (the modern replacement for branch protection) on your main branch and configure it to require a pull request before merging is allowed. By requiring at least one approver, ideally one from your CODEOWNERS file (discussed in the next section), you’ll guarantee that another human reviews each set of changes. In addition, you will want to have automated tools such as unit tests run against each pull request; these are known as status checks and will be covered under “Automation and checks” below.

2. Repository contents

Software projects don’t just consist of code. Your repository should act as a guide to collaborators, letting them know why it exists, how to use it appropriately, and the best ways to contribute. Adding a few key files (generally written using Markdown) will help other people discover your project and understand how to collaborate effectively.

README.md: This is the first file visitors to your repository will see, so it is critical to include in your repository. It should describe what your project does, how to use the repository, and any configuration needed. Additionally, a good README includes the mission of the project, what it aims to do, and why it exists. Lastly, be sure to describe how and by whom the project is maintained.

LICENSE.md: A license file defines what others can and can’t do with your code and other content. Whether your goal is to allow unrestricted use of your project, or to add special restrictions on its usage and distribution, it’s crucial to include a license. Visit choosealicense.com for guidance on which license might work best for your project, then add one to your repository.

CONTRIBUTING.md: You can reduce the amount of confusion and friction that potential contributors (and you) face by clearly defining why and how others can contribute new code, documentation, art, or other elements to your project. If the contribution steps are very simple, you might just include them in your README; but, if you find it takes more than a paragraph or two (and it usually does), it’s best to create this separate file. It should include information about the types of contributions you’re looking for, how to propose a new feature or bug fix, the process for submitting pull requests, and any specific coding standards or style guidelines contributors should follow. For a good example, take a look at the contributor guide from GitHub’s docs project.

CODEOWNERS: A CODEOWNERS file assigns one or more users who will be responsible for code in a particular part of your repository. As specified in the repository settings, these individuals will be automatically requested for review when someone opens a pull request that modifies code they own. Note that this file, unlike the others mentioned here, should not have the “.md” extension.

CODE\_OF\_CONDUCT.md: A code of conduct establishes the social norms, rules, and responsibilities that participants in your project should follow. It promotes a friendly and respectful environment for collaboration, and it is easy to add manually or by using one of GitHub’s templates!

With these files in place, your repository will be much more approachable and understandable, and you should start seeing contributions flow more freely. But if you want to go even further, there’s even more you can do to set up your project for healthy contributions.

3. Automation and checks

It’s time to enter the Matrix. As Agent Smith is fond of saying, “Never send a human to do a machine’s job.” While you generally want at least one human reviewer for each major change, you should make their job as easy as possible. GitHub’s built-in automation and CI/CD system, GitHub Actions, allows you to run workflows in response to file changes, pull requests, external triggers such as chat tools, and even cron jobs. Let’s look at a few ways this can make collaborators’ lives easier.

Linting

Linters are tools that analyze code to detect various types of errors and enforce a consistent coding style. Incorporating linters into your development process can greatly improve the readability and quality of your code, making it easier for others to understand and contribute to your project. One of the most popular is Super-Linter, which can be initially configured in a single cut-and-paste step.

Building and testing

While the exact compilers and test suites you run will be specific to the language and framework of your application, most can be executed automatically in your repository. To find the right ones, search through GitHub Marketplace’s list of Build and Test Apps & Actions, then follow the instructions specific to your preferred tool. Or, execute them by running command-line scripts and arguments in your GitHub Actions workflow.

Checks

When information is surfaced to reviewers right inside the pull request, it makes their job faster and easier, eliminating the need for them to manually run test suites or run through a physical checklist. If the automated checks fail, you can even block deployments from going out the door. Once you’ve added a linter or test suite as described above, and it has run at least once, consider configuring it as a status check in your repository settings. This will help ensure that your app is properly tested each and every time a pull request is created.

This is not a complete list, but every project is different, so also consider what other code quality, dependency management, or pre-release automation you might want to include. Then, consider how you want to deploy the project. In most cases, you’ll find there is a component in the GitHub Marketplace that provides turnkey integration with your favorite infrastructure provider, but it’s also possible to write your own GitHub Action to deploy your app after all the checks have passed. And, for high-volume enterprise projects, consider using merge queues if you start getting traffic jams on rapidly changing branches.

With these automation tools and checks in place, you can have more confidence in the quality and consistency of contributions to your repository and spend less time manually managing the process.

4. Security

Security is a paramount concern in any software project and is especially important when including a variety of collaborators who may have different levels of security training (or none at all). Fortunately, there are a few simple steps you can take to protect your code, data, and users from potential threats.

Roles

Carefully decide which roles, and thus permissions, you give to collaborators in your repository. Generally speaking, you’ll want to assign the “Read” role to the general public. “Triage” and “Write” are for trusted individuals such as members of your company or working group (but only once protected branches and checks have been set up). “Maintain” and “Admin” roles are best for your core maintainers, who are responsible for reviewing and managing what goes into production. Also consider that “Triage” and above have the ability to manage issues, discussions, and comments–so you’ll want to trust that they have the commitment and background to manage the flow of metadata surrounding your project. Enterprise customers can take advantage of custom repository roles for more granular permissions control.

Secrets management

Secrets are sensitive data like API keys, passwords, and certificates that you need to keep private. You don’t want these to be directly embedded into your code or your logs; instead, you should use either a third-party keystore or GitHub’s native secret-management tools, which can be found under the “Secrets and Variables” section of your repository settings. There, you’ll find separate sections for GitHub Codespaces (a tool described in the “Advanced Options” section below) and for GitHub Actions, because you may want to use different secrets during development than you do in production.

Security scanners

Scanning code for vulnerabilities is a complex topic, but breaks down into three major categories.

Dependencies: 80-90% of most applications’ code comes from third-party sources–the frameworks and packages we build the rest of our code on top of. GitHub Dependabot is available on all public repositories, and can be automatically enabled across entire organizations. It is able to alert you (and help provide a fix) whenever an insecure dependency is found. To ensure that Dependabot is running, check the “security” tab at the top of your repository. You can also enable dependency version updates to let you know when new versions of packages are available, so you can keep up-to-date even if an explicit vulnerability has not been identified.
Secrets: While you should already be using a secret manager as described above, we all make mistakes, and some tokens may slip through the cracks and get embedded directly into code. Secret scanning tools, provided both through third-party integrations and via GitHub Advanced Security for Enterprises, can notify you about or even block secret tokens as they are pushed into your repository.
Novel Vulnerabilities: As you write new code, you may accidentally add new vulnerabilities, either in the novel code itself or in the way you wire together existing components. There are a wide variety of ways to scan your overall application, some of which are language-dependant. Enterprises can also rely on GitHub Advanced Security’s code scanning to find a wide variety of flaws, from SQL injection to circular references, in most popular coding languages.

SECURITY.md and private vulnerability reporting

If a user or security researcher identifies a problem with your project, they need to know how to securely and responsibly report it. Include a security policy file in your repository to provide these guidelines and to help maintain the trust of your users and the wider community. Also turn on private vulnerability reporting; this allows security researchers to securely report any vulnerabilities they find!

5. Advanced options

Beyond the basics, there are a number of advanced options you can leverage to further enhance your repository’s collaboration readiness.

Issue templates

As collaborators make use of your project, they will file issues asking for bug fixes and enhancements. By default, these requests will be fairly unstructured, and you may need to loop back to the creator several times to get all the information you need. By creating a few issue templates, you can provide guidance, define which required and optional fields users will see, and set up specific options they’ll select when opening issues.

GitHub Codespaces configuration

GitHub Codespaces provides a complete, configurable dev environment on top of a repository. This allows anyone to work on your project from anywhere, without having to set up a local environment. Providing a well-configured codespace can make it much easier for others to contribute to your project and makes the project less brittle, since all developers will be working from the same configuration (eliminating the “it works on my machine but not yours” problem).

Environments

GitHub Environments let you specify where certain tasks (like deployments) should happen. They can be configured with specific protection rules, ensuring that important tasks only happen in a controlled and secure manner.

6. Next steps

Now that you’ve set up your repository, it’s time to consider the broader aspects of collaboration, including your role as a maintainer and how you engage with your community.

Responsiveness

As a maintainer, your responsiveness plays a crucial role in fostering a healthy, collaborative environment. This involves promptly addressing issues and pull requests, providing feedback, and guiding new contributors. Set aside specific times each week that you’ll dedicate toward responding to changes and remediating problems. If you want to measure how responsive your project is, check out the Metrics Action.

Project management

GitHub’s native project planning capabilities are usable both for individual projects and enterprise-wide collaboration. Set up GitHub Projects to manage your work and provide visibility to your community. This not only helps you stay organized, but also allows others to understand the current status of the project and where they can contribute.

Visibility

A well-maintained repository is of little use if nobody knows about it. Promote your project through blog posts, demos, or even dedicated project portals. The more people who know about your project, the more potential contributors and users you can attract.

Community engagement

Engaging with your community is key to fostering a healthy, collaborative environment. This might involve organizing meetups, running a project blog, or even just actively participating in discussions.

By following these standards, you can ensure that your repository is not just collaboration-ready, but also a place where a vibrant community can flourish! Print out this checklist, and use it to help guide you along each time you create (or revisit) a GitHub repository.

Get started

Download this printable checklist that you can use to ensure that you’ve covered all aspects of making your repository collaboration-ready. Or, use this handy Issue Template to create an updatable checklist right inside your own GitHub repository!

Provide context to GitHub Copilot Chat

Christopher Harrison — Tue, 10 Sep 2024 18:01:03 +0000

Context is key. This is true across all forms of communication, including with generative AI assistants like GitHub Copilot. When you're interacting with GitHub Copilot Chat, there's numerous features available to you to help point Copilot in the right direction, to help it understand what you're looking for. In turn, the suggestions you'll receive will improve! Let's walk through some of the most powerful techniques to help you get the most out of the tool.

Highlight the code

Let's say I'm trying to understand a block of code, improve its performance, or discover any security flaws. The first thing Copilot needs to know is the code I'm referring to. You can do this by highlighting the code in question. This will focus Copilot's attention on that block, and it will respond based on what it sees.

One thing you'll notice in the Chat window after you send a message is a references widget. If you expand this widget you'll be able to see what Copilot considered when crafting its answer. If you ever ask a question and the response doesn't relate to what you expected, check the references section.

Use slash commands for quick access to common questions

Copilot is great at tasks like explaining code, suggesting fixes, and generating tests. In fact, these are three of the most common workloads for Copilot, so much so that there's shortcuts to help you do these with minimal typing!

For frequently used pieces of functionality, Copilot Chat provides slash commands. These include /tests for generating unit tests or /fix to have Copilot determine a fix for buggy code. You can list all the commands available by using /help.

IMPORTANT After adding a / command, make sure you press Tab to activate it.

Expand beyond the current file with workspace

One thing you might notice about several of the slash commands is the addition of @workspace. In a nutshell, this allows Copilot to create an index of your workspace (or project), and build a response to your prompt holistically. This is rather powerful when considering multiple files is important to providing the correct code. In the example below, we have a code block which uses a service defined in a separate file. If we use /explain which includes the @workspace agent we can see the updated references widget includes not just the current file but also the source code for the service. This allows for a more robust answer.

Be specific about the important files

@workspace uses the entire workspace. But what if we know exactly what files are important to the question being asked? Let's say I'm adding some JavaScript where we need to find an element by its ID and use some CSS classes defined in a stylesheet? By using #file we can point Copilot at those specific files, which we can again see in the references widget, increasing the quality of code.

In my example I have an HTML file with an element with an ID of name-display. I have a CSS class named message-header. If I can't remember the exact names (which is pretty typical for me (and I think many developers)), I'd have to open up each file individually, explore to find the names, and then code. With #file I can point Copilot at the files, then just describe what I need. Copilot will intuit the rest for me!

Iterate and build together

GitHub Copilot has the tagline of "Your AI pair programmer". This is the perfect description of how best to interact with Copilot. If we think about talking to a coworker, or really any other person, there's often some back and forth which takes place before we find the answer we're seeking. In the example below, I asked Copilot to generate a search function by distance, which it did. But what if we wanted this to be a range rather than equality. If we provide more information we'll get the code we're looking for.

Final thoughts

As I highlighted at the top, context is key to communication. The better we help Copilot understand what we're looking for and what's important the better the responses will be. Using the techniques above to help focus Copilot's attention will allow you to move that much faster and stay in the zone.

Release Radar · August 2024: Major updates from the open source community

Michelle Duke — Fri, 06 Sep 2024 00:32:34 +0000

As winter comes to a close in the Southern Hemisphere ❄️, and summer ends in the North ☀️, developers aren't closing doors on their projects, but shipping more code. Developers are building everything from fun side hustles, to groundbreaking technology. Let's take a look at GitHub's picks for this month's Release Radar; a roundup of the open source projects that have shipped major version updates.

Bubble Tea 1.0

From Charm comes the new fun, functional, and stateful way to build interactive terminal applications. Bubble Tea is text user interface (TUI) framework built using the Go framework. Bubble Tea has been used to create all kinds of fun programs including ASCII movie art, a CLI for ChatGPT, ordering coffee from the command line, and loads more. Congrats to the team on shipping the big 1.0 🥳.

Neo.mjs 7.0

We've loved watching Neo.mjs grow. From featuring this project in the March 2022 Release Radar and our special December 2022-January 2023 Release Radar. Now Neo.mjs is back with version 7.0 🎉. Neo.mjs is a JavaScript Frontend Framework for building enterprise applications, with a focus on multi-threading. This latest version brings new syntax, enabling support to run multiple environments or versions of the framework on the same page. Check out the Medium blog post for an in-depth look at Neo.mjs and some of the new features.

Chips-n-Salsa 7.0

Don't be fooled by this delicious name, it's actually an acronym:

This is exactly what Chips-n-Salsa is, a Java library of its acronym. We featured this project in the September 2022 Release Radar back when version 6.0 was launched. Now, with update 7.0, there are some breaking changes including configurable source of randomness, enhancements to evolutionary computation, code improvements for enhanced performance, and various fixes to issues identified by static analysis tools.

PostCSS Preset Env

Who likes modern CSS? PostCSS Preset Env can help you convert modern CSS into readable browser code, by determining the polyfills needed based on the target browser or runtime environment. The latest version brings support for CSS nesting to align with the latest specifications, and the order of nested declarations and rules are preserved to better support mixins. This new update only supports Node.js 18 or higher. Check out the full list of changes in the release notes.

PlayCanvas 2.0

If you love building games, this one is for you. PlayCanvas is a WebGL and HTML5 game engine. Some of the web's most popular games have been built with PlayCanvas. The latest release has tonnes of breaking changes from removing WebGL1 support along with dozens of other legacy scripts and functions. There are also some new rendering features, materials, and blending tools. Dig into all the changes in the release notes.

And if you'd love an excuse to test out PlayCanvas, keep your eyes on the GitHub Game Off 2024 starting in November.

Material UI 6.0

If you use React, then you'll want to check out Material UI, a component library for React that implements Google's Material Design system. The latest version adds a new flag to generate CSS variables from serialised theme values. There are also new simpler ways to implement light/dark mode, the introduction of container queries, and new API for applying styles. Check out all the changes and examples in the Material UI blog. Congratulations on celebrating ten years since your first commit 🎉.

Typesense 27.0

We all make mistakes at times, and we've all made a typo here and there at some point in our lives. Typesense is here to change all that, with a typo-tolerant, in-memory, fuzzy search engine. The latest release has a new mode, better typo tolerance, support for new references and synonyms, new search parameters, and AI search improvements. Check out all the breaking changes and major updates in the Typesense release notes.

GraphQL for .NET 8.0

This is version 8.0 of GraphQL for .NET, not something for .NET 8.0 - confusing I know! GraphQL for .NET is an implementation of GraphQL specifically in .NET. The latest version brings dozens of changes from removing some deprecated methods, simplifying metadata build methods, better error messages and handling, refractor validation rules, and so much more. Check out all the changes in the release notes.

WebdriverIO 7.0

It's important to test our code to ensure it works the way we intend. WebdriverIO is a test automation framework, for e2e, unit, and component testing in the browser. It's designed for Node.js and provides support for BDD/TDD test frameworks, and can be run locally or in the cloud. The newest major release has lots of breaking changes, and a bunch of new features. Testers can use new commands, define a custom hostname for component tests, and there's support for fake timers. Check out all the major and breaking changes in the changelog.

jsdom 25.0

Here's another one for testing - jsdom, a pure JavaScript implementation of web standards. It implements the Web Hypertext Application Technology Working Group (WHATWG), HTML, and DOM standards so you can test your Node.js application. This latest version changes the prototype so the chain now stays within jsdom, avoiding potential conflicts and ensures that the behavior of objects within jsdom is consistent and predictable. This version also requires Node.js 18 or higher.

Release Radar August

Well, that’s all for this edition. Thank you to everyone who submitted a project to be featured 🙏. We loved reading about the great things you're all working on. Whether your project is featured here or not, congratulations to everyone who shipped a new release 🎉, regardless of whether you shipped your project's first version, or you launched 27.0.

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in July. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

Release Radar · July 2024: Major updates from the open source community

Michelle Duke — Fri, 02 Aug 2024 17:00:00 +0000

Whilst the best athletes in the world are competing, our developers are hard at work shipping updates for open source projects. If coding was an Olympic sport, these developers would be winning all sorts of medals. They are building everything from fun side hustles, to groundbreaking technology. Let's take a look at our staff picks for this month's Release Radar; a roundup of the open source projects that have shipped major version updates.

Vitest 2.0

I—like many others—have been using Vitest for testing frameworks. It's powered by Vite and can be used for a range of lightweight unit tests. The new version comes with simplification of the mock function, the option to run suite hooks in a stack, and the tests won't exit if global setup or config has failed. There are tonnes of new features including a new iteration of the Vitest Browser Mode, new additions, lots of bug fixes, and some breaking changes that modify the way you use Vitest for unit testing. Read up on all the changes in the Vitest changelog, and check the documentation for the migration guide.

doggo 1.0

We had to feature doggo, Bluey is an Australian National icon 🐶, and I'm Aussie after all. That aside, Doggo is a modern command line DNS client written in Golang. It outputs information in a concise manner, and supports DoH, DoT, DoQ, and DNSCrypt. It's not just called doggo for the Bluey fans and dog lovers, (even though doggos are the best, sorry cat people), it's inspired by dog written in Rust. Doggo is written in Go, so dog + go = doggo! Congratulations on shipping—and writing—your first DNS client 🥳.

Heroku CLI 9.0

If you love using or building Heroku apps, and working from the command line, then the Heroku CLI is for you. It allows you to manage all your Heroku applications from the terminal. This latest update is an architecture update, now with all the core CLI commands built on the oclif platform; an open CLI framework. This means all the output formatting is different, and there are lots of additional flags you can use to manage your apps even more seamlessly. Dig into all the changes in the Heroku release notes.

Meteor.js 3.0

Do you need a full stack framework that simplifies web and mobile application development? Then look no further than Meteor.js. It allows developers to use React, Vue, Svelte, Solid, or Blaze for the front end, with a zero-configuration setup, TypeScript support, and RPC APIs. The latest upgrade is a significant transformation of Meteor.js, that modernises the framework, and enhances its capabilities. This is achieved by integrating the latest Node.js features, moving from Fibers to native async/await, Express integration, ARM support, and package updates. Check out all the changes in the new Meteor.js docs.

Meteor.js 3 is officially here!

Denilson for Meteor ・ Jul 22 '24

#javascript #meteor #node

GoodJob 4.0

I wish I got told "good job" 👍 every single day. Rather than telling you what a good job you did, GoodJob provides a multithreaded, Postgres-based, Active Job backend for Ruby on Rails. This newest version resolves deferred database schema changes, and removes deprecated behaviour. It's been two years since the last major version update, and there are over 100 patch releases from 88 contributors including new batches, bulk enqueuing, labelled jobs, job throttling, dark mode for the web dashboard, and tonnes more. Read about them all in the GoodJob Discussion post.

JavaPermutationTools 6.0

The JavaPermutationTools (JPT) library provides Java classes and interfaces, that enable representing and generating permutations and sequences. Computations can also be performed on these permutations and sequences. The latest changes include various improvements to implementations of algorithms for randomly sampling from arrays, as well as removing previously deprecated interfaces, and a variety of fixes to issues identified by static analysis with SpotBugs. Read more about all the changes in the release notes.

cicirello / JavaPermutationTools

A Java library for computation on permutations and sequences

JavaPermutationTools (JPT): A Java library for computation on permutations and sequences

Website: https://jpt.cicirello.org/

API documentation: https://jpt.cicirello.org/api

Publications About the Library
Packages and Releases
Build Status
JaCoCo Test Coverage
Security
DOI
Other Information
Support

How to Cite

If you use this library in your research, please cite the following paper:

Cicirello, Vincent A (2018). JavaPermutationTools: A Java Library of Permutation Distance Metrics. Journal of Open Source Software, 3(31), 950. https://doi.org/10.21105/joss.00950 .

Overview

The JavaPermutationTools (JPT) library provides Java classes and interfaces, etc that enable representing and generating permutations and sequences, as well as performing computation on permutations and sequences. It includes implementations of a variety of permutation distance metrics as well as distance metrics on sequences (i.e., Strings, arrays, and other ordered data types).

Java 17+

We currently support Java 17+. See the following table for mapping between library version and minimum supported…

View on GitHub

enioka Scan 3.0

Do you have Android hardware? Are you using barcode scanners? Then enoika Scan is for you. It's an integration library for Android barcode scanners. You can write applications, without worrying about vendor lock-ins. This newest release focuses on improving the user experience, whilst including some new features. It's now easier to start developing with this library since the structure has been reworked into various modules, so you only need to find and work with the module you need. The team has now put together official documentation to make things easier to find.

Ly 1.0

This is one for our Linux and BSD devs. Ly is a lightweight display manager console and UI for Linux and BSD. Essentially it can give you a Matrix look and feel, so you can be than 10x developer. After some time, Ly has gone through a full Zig rewrite, with lots of issues fixed along the way. This leads to the first major release of Ly. Congratulations to Fairy Glade and the team 🙌.

PrimeVue 4.0

If you use Vue, then check out PrimeVue, a rich set of UI components for all your Vue based applications. The latest update includes some fixes, updates to documentation, and more. This new version is the public release of PrimeVue 4.0.0-rc.3, so you can view all the changes in the RC release notes.

go-github 63.0

Google might not be open source themselves, but they do a lot for the open source community. go-github is a Go library for accessing the GitHub API. GitHub API version 3.0 is available, and go-github makes use of this. The latest release changes the enterprise runner to also use ListRunnersOptions, as well as new feature to support the querying of custom organisation roles, which was released by GitHub in November last year. There are also lots of other changes, so make sure you check up on them all in the go-github changelog.

Release Radar July

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in June. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

Getting rid of those console.log('here') statements with GitHub Copilot

Christopher Harrison — Tue, 16 Jul 2024 17:30:55 +0000

There are two types of developers in the world - those who use console.log('here!') for debugging and then check that code in, and... Actually, I take that back. There's one type of developer in the world. Fortunately, GitHub Copilot can help us clean that up really quickly.

I've got some code with debug statements embedded. I'm also grabbing a temp variable for some data which I would normally just return directly.

async getAll(): Promise<Runner[]> {
    try {
        const runners = await this.prisma.runner.findMany();
        console.log("Runners:", runners);
        return runners;
    } catch (error) {
        console.error("Error getting all runners:", error);
        throw error;
    }
}

async getById(id: number): Promise<Runner | null> {
    try {
        console.log(id);
        return await this.prisma.runner.findUnique({
            where: { id },
        });
    } catch (error) {
        console.error(`Error getting runner by id "${id}":`, error);
        throw error;
    }
}

async getByName(name: string): Promise<Runner[]> {
    try {
        console.log(name);
        console.log('here');
        return await this.prisma.runner.findMany({
            where: { name: { contains: name } },
        });
    } catch (error) {
        let sanitized_name = name.replace(/\n|\r/g, "");
        console.error(`Error getting runners by name "%s":`, sanitized_name, error);
        throw error;
    }
}

I want to clean all of that up. I highlight the code (which sets the context for GitHub Copilot Chat), then ask GitHub Copilot Chat "Remove any debug statements and any unnecessary variables".

Within just a few moments, Copilot returns back my cleansed code which I can paste into my editor:

async getAll(): Promise<Runner[]> {
    try {
        return await this.prisma.runner.findMany();
    } catch (error) {
        console.error("Error getting all runners:", error);
        throw error;
    }
}

async getById(id: number): Promise<Runner | null> {
    try {
        return await this.prisma.runner.findUnique({
            where: { id },
        });
    } catch (error) {
        console.error(`Error getting runner by id "${id}":`, error);
        throw error;
    }
}

async getByName(name: string): Promise<Runner[]> {
    try {
        return await this.prisma.runner.findMany({
            where: { name: { contains: name } },
        });
    } catch (error) {
        console.error(`Error getting runners by name "${name}":`, error);
        throw error;
    }
}

Now, should I learn to use the debugging capabilities of Visual Studio Code instead of relying on strategies from decades ago? Probably. :D But until that happens, I can at least cleanup everything quickly and efficiently with Copilot.

I think one of the things which is often overlooked about GitHub Copilot is it's not just about creating new code, but also performing other related tasks and cleanup. When you come across a situation similar to this, where you're worried something might take a while, ask Copilot. You might just find it's able to perform the task with just a couple of quick questions. What have you been able to offload to Copilot which surprised you? Comment below!

Release Radar · June 2024: Major updates from the open source community

Michelle Duke — Fri, 05 Jul 2024 16:00:00 +0000

We've hit the halfway point of 2024. While some are catching rays on the beach or snow on the mountains—depending on your hemisphere— developer heroes are grinding away on their open source projects, shipping major updates. These hard working coders are building everything from fun side hustles, to ground breaking technology. Let's take a look at our staff picks for this month's Release Radar; a roundup of the open source projects that have shipped major version updates.

Simple Data Analysis 3.0

SDA—or Simple Data Analysis—is a high-performance JavaScript library for data analysis. The new update makes it easier to use process tabular and geospatial data. It operates seamlessly in the browser and the team behind SDA used it to tackle the 1 Billion Row Challenge—impressive stuff 😮.

FakeRest 4.0

Want a browser library that intercepts AJAX calls to mock a REST server based on JSON data? Then look no further than FakeRest. The new update has a tonne of new features including added support for Mock Service Worker (MSW), string identifiers, custom ID generation, and many more abilities. Check out the release notes for all the changes.

React-admin 5.0

Whenever I see the word "framework", I can't help but think of the Linebreakers' song "We're Gonna Build a Framework". That aside, React-admin has over 25,000 users around the world. It's a single-page application framework, allowing you to build web apps running on top of REST/GraphQL APIs, using TypeScript, React and Material Design. React-admin's latest update brings refined lists and forms, dependency update, and easier application initialisation.

Goyave 5.0

More frameworks! We all love frameworks. This one is an opinionated all-in-one Golang web framework. Goyave is focused on REST APIs, with emphasis on code reliability, maintainability and developer experience. With the newest version, Goyave has been redesigned and rewritten from the ground up. It now takes advantage of the modern language features. Read up on all the changes in their extensive release notes.

Keuss 2.0

A serverless, persistent and highly-available queue middleware. That's what Keuss is. It's built on Node.js, supports delays/schedule, and currently supports MongoDB, Redis and PostgreSQL. The latest release adds a new major backend, allowing Keuss to support queues over PostgreSQL databases. Check out the changelog for all the updates.

Node-RED 4.0

Want a low code application for event-driven applications? Then Node-RED is your go to. The new update brings a breaking change, with Node-RED now requiring Node 18.x or later. The team have added new features and updated dependencies to the editor, and there are lots of fixes within the editor. Check out the release notes for all the details.

DuckDB 1.0

What do ducks and databases have in common? They are both fast, reliable, and portable. Okay, maybe ducks aren't like that, but DuckDB is 🦆. This database provides a rich SQL dialect, with support for arbitrary and nested correlated subqueries, window functions, collations, complex types—such as arrays, structs, and maps—and several extensions. This first major release is called "Nivis", after the sadly non-existent Snow Duck, that is apparently known for its stability. Congrats to the team on shipping your very first version 🥳.

PouchDB 9.0

Speaking of databases, this one is pocket-sized. PouchDB is a JavaScript database designed to run in the browser. This latest release includes over 202 merged PRs 😮, and comes with improved stability and performance. There's the ability to streamline the automated test suites and improve in-browser testing. Read up on the major changes in the changelog.

EasyExcel 4.0

This Java-based tool is built by the team at Alibaba and is used for handling Excel files. EasyExcel can process them quickly, and can handle large file sizes. The latest release includes upgrades for poi, commons-csv, slf4j-api, and ehcache. There is now added support for jdk21. Check out all the changes in the release notes.

GitHub Roast

It's not an official release, but we felt this one deserved an honourable mention. Haimantika built this super fun—and frankly rather brutal—app that will take your GitHub username, repositories, and follower count and roast you 🔥. It's a fun way to interact with others, with lots of people sharing their roasts on social media. Built with Open AI and the GitHub API, check it out online and have yourself roasted.

// Detect dark theme var iframe = document.getElementById('tweet-1807670495208235290-216'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1807670495208235290&theme=dark" }

Release Radar June

Well, that’s all for this edition. Thank you to everyone who submitted a project to be featured 🙏. We loved reading about the great things you're all working on. Whether your project was featured here or not, congratulations to everyone who shipped a new release 🎉, regardless of whether you shipped your project's first version, or you launched 9.0.

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in May. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

Release Radar · May 2024: Major updates from the open source community

Michelle Duke — Thu, 06 Jun 2024 23:56:26 +0000

While the Northern Hemisphere springs into a fresh era 🌷, the Southern says goodbye to Fall (or Autumn as we say Down Under 🍂). As the seasons change, our developers are changing, updating, and shipping their projects. There are a tonne of great projects featured here, everything from weekend hobbies, to world changing technology. Let's take a look at our staff picks for this month's Release Radar; a roundup of the open source projects that have shipped major version updates.

Angular 18.0

Those building mobile and desktop web applications might be familiar with Angular, a development platform for building using TypeScript, JavaScript, and other languages. The latest release brings a new home for Angular Developers with their new website, experimental support for zoneless change detection, lots of server-side rendering improvements, more stable controls, and lots more. Check out all the changes and what these mean for Angular devs on the Angular blog post.

Web Check 1.0

Looking for comprehensive, on-demand intelligence for any website? Look no further than Web Check. With Web Check, you can see insights for any website, uncover potential attack vectors, analyse server architecture, view security configurations, and see what technologies drive a particular site. Congrats on shipping out the first major version 🥳.

Apache Skywalking 10.0

Are you working on microservices, cloud native, and container-based architectures? Then you need to check out Apache Skywalking. It's an Application Performance Monitoring (APM) system, that provides monitoring, tracing, and diagnosing capabilities for distributed systems in Cloud Native architectures. This latest update has hundreds of changes including support for Java 21 runtime, new functions and parameters, the addition of Golang as a supported language for AMQP, Kafka, RocketMQ, and Pulsar, support for multiple labels in metrics, and tonnes more. Check out all changes in the very comprehensive release notes. All the Apache Skywalking metrics are available via Grafana.

Grafana 11.0

Speaking of metrics and Grafana, this popular project gets a major update too. As shown in the image above, Grafana is a data visualisation and composable observability platform. With Grafana you can query, visualise, alert on, and understand your metrics wherever that data may sit. The latest update adds lots of new features and enhancements such as a slightly refreshed UI, reducing the set of fields that could trigger an alert state change, the removal of Loki's API restrictions on resource calls, and lots more. Check out all the changes in the changelog.

Tasmota 14.0

Firmware and embedded systems engineers will love this project; Tasmota is firmware for ESP8266 and ESP32 based devices that allows you to more easily configure your devices. The catch with this new update is that direct migration for versions earlier than 8.1 are no longer supported. If you're using anything higher, you can directly migrate to this latest version. Tasmota 14.0 adds a bunch of new commands, support for new hardware such as temperature and pressure sensors, and lots more. Read up on all the new devices, modules, and how to migrate in the Tasmota release notes.

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX Written for PlatformIO.

In light of current events we like to support the people behind PlatformIO Project, especially Ivan Kravets, and wish them the strength to help stop the war. See platformio-is-ukrainian-project-please-help-us-stop-the-war for what you can do.

Easy install

Easy initial installation of Tasmota can be performed using the Tasmota WebInstaller.

If you like Tasmota, give it a star, or fork it and contribute!

See RELEASENOTES.md for release information.

Firmware binaries can be downloaded from http://ota.tasmota.com/tasmota/release/ or http://ota.tasmota.com/tasmota32/release/ for ESP32 binaries.

Development

See CHANGELOG.md for detailed change information.

Unless your Tasmota powered device exhibits a problem or lacks a feature that you need, leave your device alone - it works so don’t make unnecessary changes…

View on GitHub

croc 10.0

Do you have more than one computer? Ever had 'fun' trying to get files from one computer to the other? Croc is here to save you. This CLI tool allows any two computers to securely transfer files and folders. You can transfer multiple files, including cross-platform (Windows, Linux, Mac), and you can use a proxy. The newest version of croc has a few of the usual 🐛 fixes and has a new way to define ports.

ρμ 4.0

Pronounced rho mu, ρμ is a Java library of randomization enhancements and other math utilities. In this latest update, ρμ makes improvements to the generation of random pairs and triples of distinct integers, adds support for generating streams of random pairs and triples of distinct integers, adds methods for efficiently shuffling arrays and lists, removes a couple of previously deprecated classes, and includes some improvements to internal library code. Check out the changelog for all the updates.

cicirello / rho-mu

ρμ - a Java library of Randomization enHancements and Other Math Utilities

ρμ - Java library of Randomization enHancements and Other Math Utilities

Website: https://rho-mu.cicirello.org/

API documentation: https://rho-mu.cicirello.org/api/

Publications About the Library
Packages and Releases
Build Status
JaCoCo Test Coverage
Security
DOI
Other Information
Support

How to Cite

If you use this library in your research, please cite the following paper:

Cicirello, V. A., (2022). ρμ: A Java library of randomization enhancements and other math utilities. Journal of Open Source Software, 7(76), 4663, https://doi.org/10.21105/joss.04663.

Overview

ρμ is a Java library of Randomization enHancements and Other Math Utilities (rho mu). It includes implementations of various algorithms for efficiently randomly sampling combinations of indexes into arrays and other sequential structures. It also includes efficient implementations of random number generation from distributions other than uniform, such as Gaussian, Cauchy, etc. Additionally, it includes implementations of other math functions that are either needed by the randomization utilities…

View on GitHub

Social Switch 1.0

Have you ever tried to share a social media post, and your friend on the other end can't see it because they don't have an account for that particular platform? Or maybe you want to look at a post and remain anonymous, Social Switch is here for you. Available as a Chrome, Firefox, or Firefox for Android extension, Social Switch allows you to share social media links from Instagram and TikTok URLs and users don't need to reveal their identity or log into their accounts. Congrats to the team on shipping your very first version 🥳.

Simple Icons 12.0

Having featured Simple Icons in the past, this project continues to make updates. Simple Icons now has over 3100 free SVG icons for all your favourite brands. The latest update provides more than a dozen new icons, and some revamped icons too. Check them all out and download them for your projects via the Simple Icons website.

NetBox 4.0

If you're a network engineer, then you need to know about NetBox. It exists to empower you, and provides an accessible data model for all things networked. There's a single robust user interface and programmable APIs for everything from cable maps to device configurations. This latest update changes the format for GraphQL queries, a completely refreshed UI, support for dynamic REST API fields, and lots more. Read up on all the breaking changes and dig into the migration guide to ensure you're up to date and compatible.

Release Radar May 2024

Well, that’s all for this edition. Thank you to everyone who submitted a project to be featured 🙏. We loved reading about the great things you're all working on. Whether your project was featured here or not, congratulations to everyone who shipped a new release 🎉, regardless of whether you shipped your project's first version, or you launched 18.0.

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in April. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

Gamedev.js Open Source Challenge Winners 🏆

Lee Reilly — Thu, 16 May 2024 23:54:14 +0000

The Gamedev.js 2024 game jam just wrapped up, where participants had 13 days to build HTML5 games based on the theme POWER ⚡

This year we sponsored the "Open Source Challenge" - encouraging participants to share the source code (with a license of their choosing).

Here are the top five entries as voted on by all of the participants - ranging from strategic mazes and competitive puck battles to power management in outer space. Enjoy!

Mech Motion 🥇

^{by @Chocobois}

Play · View source · Read reviews

Mech Motion powers up your strategic circuits, tasking you to maneuver a robotic helper through mazes using cleverly coded movement cards. Get charged up to collect all the energy cells before your bot runs out of juice in this electrifying puzzle challenge!

Puckit! 🥈

^{by @johnedvard}

Play · View source · Read reviews

Charge into Puckit! where you power up your puck to strategically knock pint-sized pawns into pits. Harness your finger finesse or masterful mouse moves to score, shock, and showcase your prowess in this dynamic duel—just don’t fall into your own trap!

Gleep Gym 🥉

^{By @MiamoAlex, @Rusalka, @mo_01, @sukai909}

Play · View source · Read reviews

Jump into Gleep Gym, where you'll flex your power levels against quirky gym members in a flash of nostalgic, Warioware-esque mini-games. Are you buff enough to conquer their challenges, or will you need a power shake-up in this electrifying, seizure-aware sprint to the stars?

IONCLAD 🏅

^{by @BethFromAbove, @jonathan-rose, @Kimbsy}

Play · View source · Read reviews

Blast into IONCLAD where survival hinges on your quick reflexes and power management prowess. Navigate your cannon, obliterate enemy ships, rescue allies, and unleash mega-bombs—just try not to blackout in this high-voltage cosmic showdown!

PowerLess Hotel 🏅

^{By @iplnkr}

Play · View source · Read reviews

In PowerLess Hotel, stealthily navigate a haunted hotel to restore power, armed only with a torch and the peculiar ability to summon room service for spectral disturbances. Will you light up the rooms or succumb to the shadows? Prepare to adjust brightness and tip your way through this eerie, electrifying escapade!

In addition to bragging rights, the creators above games won themselves free GitHub Copilot for a year and $60 to spend in the GitHub Shop.

Massive congratulations to everyone who participated, rated, and reviewed all those games. And shout out to @end3r for another incredible game jam! 🤘🏻

Pst! One last thing: there's another big game jam happening in November. This one lasts an entire month, and you can use any programming language, game engine, open source libraries, or AI tool that you like.

Join now and be amongst the first to know the secret theme.

Release Radar · April 2024 Edition: Major updates from the open source community

Michelle Duke — Fri, 03 May 2024 11:46:25 +0000

We're right into the thick of the year, and developers worldwide are shipping software in all directions. Whilst we've been busy with GitHub Galaxy, our community has been sending out major updates for top open source projects. We've taken a look at dozens of them and have curated a list, showing you what the project is, and its major updates. Let's take a look at our staff picks for this month's Release Radar.

ESLint 9.0

Do you have the need to find and fix problems in your JavaScript? Then ESLint is for you. With over 120 million downloads each month, it's definitely one of the most popular projects out there. The latest version introduces a new configuration system, designed to simplify available configuration options. Old and deprecated rules have been removed, and a new configuration inspector has been added. Check out the blog for all the highlights, and a migration guide.

Podlite 1.0

Flexibility and ease of use is important in the software development lifecycle. That's why Podlite was built; a lightweight block-oriented markup language designed for simplicity. It's a universal markup language, not bound by any specific domain, programming language, or concept. Podlite is the type of language that's perfect for documentation, educational materials, or blogging. Congrats to the team on shipping your first major version 🥳.

Podlite v1.0 released: A lightweight block-oriented markup language for organizing knowledge

Alexandr Zahatski ・ Apr 23 '24

#podlite #webdev #opensource #architecture

Quill 2.0

Speaking of text, here's another one for you. Quill is a rich text editor also built for compatibility and extensibility. The latest version prevents mistakenly overriding theme default toolbar settings, and Quill is now a valid ESM package for better ecosystem. There's nested Quill support, improved spelling support, and improved support for pasting from Google Docs and Microsoft Word. Check out all the changes on the Slab website.

Spoon 11.0

The creators at Spoon claim that "🥄 is made with ❤️, 🍻 and ✨"! And why not?! Spoon is a metaprogramming library to analyze and transform Java source code by parsing source files to build a well-designed AST (Abstract Syntax Tree). The latest version supports Java 17 and the modelling of receiver parameters has been changed. Read all about the changes in the release notes.

Traefik 3.0

Pronounced "traffic", Traefik is a modern HTTP reverse proxy and load balancer aimed at making deploying microservices easier. It integrates with your existing infrastructure components such as Docker, Kubernetes, and others, and configures itself automatically and dynamically. The latest version adds lots of new options and enhancements such as adding healthcheck options, support for custom headers, and more. Read the migration guide on how to update to the latest version which is now required due to breaking changes.

Penpot 2.0

Imagine designers and coders working seamlessly together. That's what Penpot aims to do. It's a tool where designers can create stunning designs, interactive prototypes, and design systems at scale. Developers then have ready-to-use code, which makes their workflows faster and more efficient. Penpot's latest version receives a new grid CSS layout, new UI, new components system, and more components. Oh and there's now light AND dark mode 🎉.

Loki 3.0

It's like Prometheus, but for logs. Okay it's not really to do with the Norse or Greek gods, instead Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by the open source project Prometheus. Built by Grafana Labs, Loki is designed for ease of use. Instead of indexing the contents of the logs, Loki provides a set of labels for each log stream. The latest update includes query acceleration with Bloom filters, native OTel support, Helm charts, and more. Check out the changelog for all the major changes and deprecations.

Typesense 26.0

Have you ever tried to look up something, only to realise your search engine doesn't recognise your typos? Typesense to the rescue! It's a fast, typo-tolerant search engine built for an easier browsing experience. The latest version comes with new features such as built-in conversational search, image search, voice search, analytics, and more. Dive into the release notes for the full list of changes and enhancements.

Release Radar April 2024

Well, that’s all for this edition. Thank you to everyone who submitted a project to be featured 🙏. We loved reading about the great things you're all working on. Whether your project is here or not, congratulations to everyone who shipped a new release 🎉, regardless of whether you shipped your project's first version, or you launched 26.0.

If you missed our last Release Radar, check out the amazing open source projects that released major version projects in March. We love featuring projects submitted by the community. If you're working on an open source project and shipping a major version soon, we'd love to hear from you. Check out the Release Radar repository, and submit your project to be featured in the GitHub Release Radar.

Release Radar • March 2024 Edition

Michelle Duke for GitHub ・ Apr 8 '24

#github #opensource #community #news