Repository navigation
Release issue ci job - #8819
Draft
pabzm wants to merge 2 commits into
Draft
Release issue ci job#8819pabzm wants to merge 2 commits into
pabzm wants to merge 2 commits into
Conversation
This * creates a new issue, * sets the title, `overview` label, and `next` milestone, * automatically adds the ID of the previous release issue, * posts a link to the new issue in the previous release issue. The job is pinned to this repo, and runs only on manual trigger, which means no one but us maintainers can run it. Signed-off-by: Pablo Zmdl <pablo@nextcloud.com> AI-assistant: Claude Opus 5.5
Signed-off-by: Pablo Zmdl <pablo@nextcloud.com> AI-assistant: Claude Opus 5.5
Member
Author
|
@szaimen I didn't test it yet, since that would create issues, etc., which I didn't want to do out of the blue. Rather I'd like to hear about your general feeling about this: can we go this route? |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The generated commit lacks required DCO sign-off, and workflow-run correlation can monitor the wrong release run.
4 open findings
What changed in this PR
Automates recurring release-ticket creation and the three-stage AIO release process.
Changes:
- Adds workflows for building, beta promotion, and stable publication.
- Adds shared release orchestration scripts.
- Adds automated recurring release-issue creation.
| File | Description |
|---|---|
.github/workflows/release-1-build.yml |
Dispatches version bump and image build. |
.github/workflows/release-2-beta.yml |
Dispatches testing and beta promotion. |
.github/workflows/release-3-stable.yml |
Dispatches stable publication. |
.github/workflows/create-release-issue.yml |
Creates recurring release issues. |
.github/scripts/release-build.sh |
Commits the version and starts builds. |
.github/scripts/release-beta.sh |
Tests, promotes, and creates a prerelease. |
.github/scripts/release-stable.sh |
Publishes stable images and closes the milestone. |
.github/scripts/release-lib.sh |
Provides shared release helpers. |
.github/scripts/create-release-issue.sh |
Builds and submits the release issue. |
.github/release-issue-template.md |
Defines the release checklist. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| # `gh workflow run` doesn't return the run ID, so wait for a run newer than the last known one. | ||
| while [ -z "$id" ]; do | ||
| sleep 5 | ||
| id="$(gh run list -R "$1" -w "$2" -L 1 --json databaseId --jq ".[] | select(.databaseId > $before) | .databaseId")" |
| - [ ] run [Release 2](https://github.com/nextcloud/all-in-one/actions/workflows/release-2-beta.yml) with the Nextcloud version that new instances can install directly: runs the E2E tests, deploys from develop to beta, creates the `vX.Y.Z Beta` pre-release with the autogenerated changelog and a Discussion, renames the `next` milestone to the version number, creates a new `next` milestone and moves all open issues/PRs to it | ||
| - [ ] post in all issues and discussions that were fixed/implemented that this is now released with the new beta version and post how to switch to the beta channel (e.g. `This is now released with X.Y.Z Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel`) | ||
| - [ ] wait a week and see if new bugs get reported and don't merge any PR into the main branch of this repo in the meantime! | ||
| - [ ] if not, publish to latest as describe below; if yes simply close this milestone and create a new one that includes the bugfixes and starts from the beginning of this guide |
| [[ "$(git remote get-url origin)" == *"$GH_REPO"* ]] || die "origin must point to $GH_REPO" | ||
|
|
||
| echo "$VERSION" > "$VERSION_FILE" | ||
| git commit -m "chore(release): bump AIO version to $VERSION" -- "$VERSION_FILE" |
| @@ -0,0 +1,23 @@ | |||
| name: Create release issue | |||
This branch has not been deployed
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.
This is an approach to reduce the number of manual clicks we are doing for release management.
The workflow can only be triggered manually, thus only by maintainers.
Summary
3. to review, feature component)AI (if applicable)