Renovate opens bump PRs for new Upstream Versions #8

New issue

Closed

opened 2026-09-30 13:14:53 +00:00 by piscis · 1 comment

piscis commented

2026-09-30 13:14:53 +00:00

Owner

Copy link

What to build

Renovate, not a custom workflow, opens the bump PRs (decided in the grilling on #5). renovatebot already runs in the org and opened onboarding PR #13 here; build on it (merge or supersede it).

In this repo's renovate.json:

A custom regex manager for pin.env using the git-tags datasource against the canonical Upstream (https://git.b4mad.industries/agentic-forges/forgejo-mcp, ADR 0002). It updates UPSTREAM_VERSION and, as the digest, UPSTREAM_COMMIT together.
No postUpgradeTasks. Renovate doesn't touch REBUILD or REBUILD_OF: after a bump, REBUILD_OF no longer matches UPSTREAM_VERSION, so the Rebuild counts as 1 (#16, ADR 0003).
"enabled": true: the self-hosted bot skips repos without it (see vicoli/forgejo-renovate-bot's README).
Only stable semver tags (ignore pre-releases). The PR description links the Upstream release or changelog.

PRs opened by renovatebot use its own token, so they trigger the PR CI (#6).

Acceptance criteria

With the Pin one version behind, Renovate opens exactly one bump PR with the correct version and commit, and the build tags it as Rebuild 1
The bump PR triggers the PR CI (build and smoke test), and the Dockerfile's commit check passes
While that PR is open, Renovate updates it rather than opening a duplicate
With the Pin already at the newest Upstream Version, Renovate does nothing
Pre-release tags are ignored

Blocked by

Context: see GLOSSARY.md (Upstream, Upstream Version, Image, Rebuild, Consumer, Pin) and docs/adr/ (0001 build from Upstream source for multi-arch, 0002 canonical Upstream not the Codeberg mirror, 0003 tag scheme and immutable Rebuild tags, 0004 public org vicoli-oss).

## What to build Renovate, not a custom workflow, opens the bump PRs (decided in the grilling on #5). `renovatebot` already runs in the org and opened onboarding PR #13 here; build on it (merge or supersede it). In this repo's `renovate.json`: - A **custom regex manager** for `pin.env` using the `git-tags` datasource against the canonical Upstream (`https://git.b4mad.industries/agentic-forges/forgejo-mcp`, ADR 0002). It updates `UPSTREAM_VERSION` and, as the digest, `UPSTREAM_COMMIT` together. - **No `postUpgradeTasks`.** Renovate doesn't touch `REBUILD` or `REBUILD_OF`: after a bump, `REBUILD_OF` no longer matches `UPSTREAM_VERSION`, so the Rebuild counts as 1 (#16, ADR 0003). - `"enabled": true`: the self-hosted bot skips repos without it (see `vicoli/forgejo-renovate-bot`'s README). - Only stable semver tags (ignore pre-releases). The PR description links the Upstream release or changelog. PRs opened by `renovatebot` use its own token, so they trigger the PR CI (#6). ## Acceptance criteria - [ ] With the Pin one version behind, Renovate opens exactly one bump PR with the correct version and commit, and the build tags it as Rebuild `1` - [ ] The bump PR triggers the PR CI (build and smoke test), and the Dockerfile's commit check passes - [ ] While that PR is open, Renovate updates it rather than opening a duplicate - [ ] With the Pin already at the newest Upstream Version, Renovate does nothing - [ ] Pre-release tags are ignored ## Blocked by - #6 - #5 - #16 Context: see `GLOSSARY.md` (Upstream, Upstream Version, Image, Rebuild, Consumer, Pin) and `docs/adr/` (0001 build from Upstream source for multi-arch, 0002 canonical Upstream not the Codeberg mirror, 0003 tag scheme and immutable Rebuild tags, 0004 public org `vicoli-oss`).

piscis added the

ready-for-agent

label

2026-09-30 13:14:53 +00:00

piscis added a new dependency

2026-09-30 13:14:53 +00:00

#6 CI builds and smoke-tests the Image on every PR

piscis added a new dependency

2026-09-30 13:14:53 +00:00

#5 Set up vicoli-oss, move the repo, and store the package token

~~piscis referenced this issue 2026-09-30 13:47:16 +00:00~~

Set up vicoli-oss, move the repo, and store the package token #5

piscis changed title from ~~Daily workflow opens bump PRs for new Upstream Versions~~ to Renovate opens bump PRs for new Upstream Versions

2026-09-30 13:47:16 +00:00

piscis referenced this issue

2026-09-30 13:47:16 +00:00

README: using the Image in a coding project #9

piscis referenced this issue

2026-09-30 13:47:16 +00:00

Set up vicoli-oss, move the repo, and store the package token #5

piscis referenced this issue

2026-09-30 13:47:29 +00:00

docs: publish the Image from a public vicoli-oss org #15

piscis added a new dependency

2026-09-30 14:05:12 +00:00

#16 Pin records which Upstream Version the Rebuild counts against

piscis referenced this issue

2026-09-30 14:06:32 +00:00

Set up vicoli-oss, move the repo, and store the package token #5

piscis added the

enhancement

label

2026-09-30 14:34:20 +00:00

piscis self-assigned this

2026-09-30 15:24:47 +00:00

piscis referenced this issue from a commit

2026-09-30 15:27:51 +00:00

feat(renovate): open bump PRs for new Upstream Versions (#8)

piscis referenced this issue from a pull request that will close it,

2026-09-30 15:29:53 +00:00

feat(renovate): open bump PRs for new Upstream Versions #27

piscis closed this issue

2026-09-30 15:35:17 +00:00

piscis referenced this issue from a commit

2026-09-30 15:35:26 +00:00

test(renovate): set the Pin one Upstream Version behind for the live bot check (#8)

piscis referenced this issue

2026-09-30 15:50:34 +00:00

ci: publish the Image on push to main (#7) #28

piscis commented

2026-09-30 17:07:55 +00:00

Author

Owner

Copy link

Live bot check, 2026-09-30 (Renovate 43, renovatebot):

Pin one version behind → exactly one bump PR. I set the Pin to v3.1.0 on main (c261ae2), and renovatebot opened #29 on renovate/forgejo-mcp. The diff changes only UPSTREAM_VERSION → v3.2.0 and UPSTREAM_COMMIT → e30bb7e2e45c0e447506b5df1fe83ebce4b43944, the commit the tag points to, not the tag object 931a525d. REBUILD/REBUILD_OF are untouched, and make print-tag on the branch gives 3.2.0-r1. The body links the Upstream release and embeds its release notes.
The bump PR triggers PR CI, which passed on the bot's own token (ci / build (pull_request) on f2ec6c4e, including the Dockerfile's commit check). I merged #29, which restored the Pin.
Pin current → nothing. The bot's next pass (17:07 UTC) deleted the merged branch and opened no new PR. The old renovate/configure branch is gone too, and there's no Dependency Dashboard issue.
Pre-releases ignored. allowedVersions blocks them, shown offline in #27. Upstream has had no pre-release tag since, so this is not live-verified.
Updates instead of duplicating. Not live-verified: I merged #29 before a second bot run, so the Pin wouldn't sit behind on main. The config ensures it: renovate/forgejo-mcp is the only branch, even across majors.

The bot got stuck at first. It couldn't push to this repo because the vicoli-oss Bots team only had read, and Renovate aborts on repos without push. I raised the team to write, which also raised the releases, wiki and projects units to write.

Live bot check, 2026-09-30 (Renovate 43, `renovatebot`): - [x] **Pin one version behind → exactly one bump PR.** I set the Pin to `v3.1.0` on main (`c261ae2`), and `renovatebot` opened #29 on `renovate/forgejo-mcp`. The diff changes only `UPSTREAM_VERSION` → `v3.2.0` and `UPSTREAM_COMMIT` → `e30bb7e2e45c0e447506b5df1fe83ebce4b43944`, the commit the tag points to, not the tag object `931a525d`. `REBUILD`/`REBUILD_OF` are untouched, and `make print-tag` on the branch gives `3.2.0-r1`. The body links the Upstream release and embeds its release notes. - [x] **The bump PR triggers PR CI**, which passed on the bot's own token (`ci / build (pull_request)` on `f2ec6c4e`, including the Dockerfile's commit check). I merged #29, which restored the Pin. - [x] **Pin current → nothing.** The bot's next pass (17:07 UTC) deleted the merged branch and opened no new PR. The old `renovate/configure` branch is gone too, and there's no Dependency Dashboard issue. - [x] **Pre-releases ignored.** `allowedVersions` blocks them, shown offline in #27. Upstream has had no pre-release tag since, so this is not live-verified. - [ ] **Updates instead of duplicating.** Not live-verified: I merged #29 before a second bot run, so the Pin wouldn't sit behind on main. The config ensures it: `renovate/forgejo-mcp` is the only branch, even across majors. The bot got stuck at first. It couldn't push to this repo because the `vicoli-oss` **Bots** team only had `read`, and Renovate aborts on repos without push. I raised the team to `write`, which also raised the releases, wiki and projects units to write.

No Branch/Tag specified

main

piscis/32-claude-setup-update

piscis/forgejo-issue-8-implement

piscis/forgejo-16-implement

piscis/vicoli-oss-descriptions-add

piscis/forgejo-4-multi-arch-implement

piscis/forgejo-mcp-docker-image-plan

piscis/matt-pocock-skills-setup

piscis/mcp.json-context7-config

No results found.

Labels

Clear labels

bug

Something is broken

enhancement

New feature or improvement

needs-info

Waiting on reporter for more information

needs-triage

Maintainer needs to evaluate this issue

ready-for-agent

Fully specified, ready for an AFK agent

ready-for-human

Requires human implementation

wayfinder:grilling

Wayfinder ticket: grilling

wayfinder:map

Wayfinder map: Notes / Decisions-so-far / Fog

wayfinder:prototype

Wayfinder ticket: prototype

wayfinder:research

Wayfinder ticket: research

wayfinder:task

Wayfinder ticket: task

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

piscis

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on

#6 CI builds and smoke-tests the Image on every PR

vicoli-oss/docker-forgejo-mcp

#5 Set up vicoli-oss, move the repo, and store the package token

vicoli-oss/docker-forgejo-mcp

#16 Pin records which Upstream Version the Rebuild counts against

vicoli-oss/docker-forgejo-mcp

Reference

vicoli-oss/docker-forgejo-mcp#8

Reference in a new issue

Repository

vicoli-oss/docker-forgejo-mcp

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns