update-release | Github release smartly , with a freshly built asset | Continous Integration library

update-release is a TypeScript library typically used in Devops, Continous Integration applications. update-release has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This Github action allows you, and anyone you choose, to easily get access to files created as part of your continuous integration on Github runners. If you use Github to build digital assets such as zip files or executables, this action makes accessing your build products easy for everyone involved with your project. Github has a very walled-garden, hands-on philosophy about what a "release" should be. According to Github, a release must be tagged by a human; release artifacts must be built by a human; and then specific binary assets must be uploaded by a human into that release. This update-release action breaks down those expectations. Any branch, tag, or indeed any Github checkin at all, can now be continuously integrated via Github runners, with its build products continuously accessible to you, your team, or the world, via Github releases. With this action, Github runners can build, test, and package artifacts on any Github ref, branch, or tag. This action continuously creates and updates the necessary Github tags and releases with these artifacts. This update-release action makes sane choices all the way along this process, but it lets you override those choices easily. Every time a Github runner builds your source code, update-release creates or updates a Github release for your assets, and then uploads the freshly built assets into your release. Existing releases are reused, and existing assets with the same names are replaced. Because this action is written in TypeScript and executes in node.js, it runs on all Github's supported build runner platforms. These include Windows, MacOS, and Ubuntu as of this writing.