releases
Here are 171 public repositories matching this topic...
Erlang build tool that makes it easy to compile and test Erlang applications and releases.
-
Updated
Jul 13, 2021 - Erlang
Why you should bump your Android app minsdk?
-
Updated
Jan 30, 2018
A central community-backed place to request and give help when upgrading your app.
-
Updated
Jun 18, 2021 - JavaScript
Dashboard for your Deployment pipeline https://dashboardhub.io/
-
Updated
Mar 29, 2021 - TypeScript
Library for parsing and generating a changelog, or releasenotes, from a GIT repository
-
Updated
Jul 15, 2021 - Java
A repository containing experimental releases of Notable.
-
Updated
Jan 16, 2021
Allows you to receive notifications of new releases of software on GitHub in Telegram
-
Updated
Sep 4, 2020 - JavaScript
All about your Github account, public and private activity, watch stars, followers and much more.
-
Updated
Aug 29, 2019 - JavaScript
A command-line tool for managing release assets on a GitHub repository.
-
Updated
Mar 14, 2021 - JavaScript
Git Releases allows you to directly link to the assets of your latest release on GitHub.
-
Updated
Apr 15, 2021 - Go
-
Updated
Jul 15, 2021 - Go
A Swift package for resolving released versions from a Git repository
-
Updated
May 16, 2021 - Swift
A GitHub action that creates releases for Sentry.io.
-
Updated
Jul 21, 2021 - JavaScript
-
Updated
Jul 20, 2021 - TypeScript
Git utility to create tags in order to identify specific releases
-
Updated
Jul 16, 2021 - Shell
[GitHub Action] Get ${version} from package.json and git tag ${version} for the repository.
-
Updated
Jul 3, 2021 - TypeScript
Github repository CLI Release Checker
-
Updated
Apr 7, 2018 - Go
Release exporter for GitHub and GitLab
-
Updated
Jul 14, 2021 - Python
Improve this page
Add a description, image, and links to the releases topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the releases topic, visit your repo's landing page and select "manage topics."


Describe the bug
The diagram detailing when hooks (especially release lifecycle hooks) are invoked for each command are incredibly useful when writing a plugin or trying to understand how different plugins will behave together.
However, when tracing through the code, I've noticed the following inconsistency(ies) between the diagram and the