Skip to content

ci: add release-3.10 branch to Dependabot config #775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 6, 2022
Merged

ci: add release-3.10 branch to Dependabot config #775

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4371926
ci: add release-3.10 branch to Dependabot config
tri-adam May 4, 2022
7f5892b
docs: Dependabot tweaks in release proceedure
tri-adam May 4, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,8 @@ updates:
schedule:
interval: "daily"
target-branch: release-3.9
- package-ecosystem: "gomod" # See documentation for possible values
directory: "/" # Location of package manifests
schedule:
interval: "daily"
target-branch: release-3.10
12 changes: 8 additions & 4 deletions RELEASE_PROCEDURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,13 +28,17 @@ When a new 3.Y.0 minor version of SingularityCE is issued the release process
begins by branching, and then issuing a release candidate for broader testing.

When a new 3.Y.Z patch release is issued, the branch will already be present,
and steps 1-2 should be skipped.
and steps 1-4 should be skipped.

1. From a repository that is up-to-date with master, create a release branch
e.g. `git checkout upstream/master -b release-3.8`.
1. Push the release branch to GitHub via `git push upstream release-3.8`.
1. Examine the GitHub branch protection rules, to extend them to the new release
branch if needed.
1. Update the `.github/dependabot.yml` configuration so that dependabot is
tracking the new stable release branch. Do not remove the previous stable
release branch from the configuration yet, as it should be monitored until
the final release of a new 3.Y.0 version.
1. Modify the `README.md`, `INSTALL.md`, `CHANGELOG.md` via PR against the
release branch, so that they reflect the version to be released.
1. Apply an annotated tag via
Expand Down Expand Up @@ -81,7 +85,7 @@ covered by tests.
history from the RC process etc. is captured on `master`.
1. If the release is a new major/minor version, move the prior `release-3.x`
branch to `vault/release-3.x`.
1. If the release is a new major/minor version, update the
`.github/dependabot.yml` configuration so that dependabot is tracking the new
stable release branch.
1. If the release is a new final major/minor version, update the
`.github/dependabot.yml` configuration to remove the prior stable release
branch.
1. Start scheduling / setting up milestones etc. to track the next release!