ci: add Dependabot configuration and automated release pipeline#5
Merged
ci: add Dependabot configuration and automated release pipeline#5
Conversation
…ency management and releases
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces the full automated dependency management and release pipeline for the Runtime Node project. It configures Dependabot to monitor and raise daily Docker base image update PRs against
develop, adds a workflow to automatically merge approved Dependabot PRs, adds a workflow to create arelease/v*branch and open a PR tomainwhenever Dependabot merges intodevelop, and adds a workflow to automatically tag and publish a GitHub Release whenever a merge lands onmain.Together these four pieces close the loop on fully automated releases — from a Dependabot Node.js version bump all the way through to a tagged GitHub Release — without any manual intervention required. A
VERSIONfile is also introduced as the source of truth for the SemVer component of the release tag.Files Changed
Added:
.github/dependabot.ymlworkflows/auto-merge-dependabot.ymlrelease-from-develop.ymltag-and-release.ymlVERSIONModified:
Deleted:
Key Changes
.github/dependabot.yml— configures Dependabot on thedockerecosystem targeting the rootDockerfile, running on adailyschedule against thedevelopbranch, with thechorecommit prefix, a/branch name separator,dependencies,docker, andnodelabels applied, and a maximum of 1 open PR at a time..github/workflows/auto-merge-dependabot.yml— triggered on PR open, synchronize, and reopen events; auto-merges (merge commit strategy) any PR where the actor isdependabot[bot]and thedependencieslabel is present, using the built-inGITHUB_TOKENwithcontents: writeandpull-requests: writepermissions..github/workflows/release-from-develop.yml— triggered on every push todevelop, but gated to only run when the actor isdependabot[bot]; extracts the Node.js version from theDockerfilevia agrepregex, reads the SemVer from theVERSIONfile, constructs arelease/v<semver>-<node_version>branch name, pushes the branch, and opens a PR tomainusingpeter-evans/create-pull-request@v5with a templated PR title and structured PR body..github/workflows/tag-and-release.yml— triggered on every push tomain; extracts the Node.js version from theDockerfile, reads the SemVer from theVERSIONfile, computes the full tag asv<semver>-<node_version>, creates and pushes an annotated Git tag viagit tag -a, and publishes a GitHub Release usingactions/create-release@v1with the tag name, release name, and an auto-generated release body including the Node version.VERSION— a plain text file containing1.0.0, serving as the SemVer source of truth consumed by bothrelease-from-develop.ymlandtag-and-release.ymlto construct release tags.