fix: openbao-plugins github field points to wrong release tag #117

New Issue

2026-05-02T01:46:18+10:00

unkinben commented

2026-05-02 01:46:18 +10:00

Problem

Three packages (openbao-plugin-secret-consul, openbao-plugin-secret-nomad, openbao-plugins) all point to github: openbao/openbao-plugins. The latest release tag on that repo is secrets-nomad-v0.1.5, which is not a clean version string.

tools/update-gh reports:

openbao-plugin-secret-consul: 0.1.0 -> secrets-nomad-v0.1.5
openbao-plugin-secret-nomad:  0.1.5 -> secrets-nomad-v0.1.5
openbao-plugins:              1.0.0 -> secrets-nomad-v0.1.5

The tag secrets-nomad-v0.1.5 appears to be a plugin-specific release tag, not a repo-wide release. Each package likely needs its own tag prefix filter.

Options

Add a tag_filter field to metadata.yaml (e.g. tag_filter: "secrets-consul-v") so update-gh queries the right release
Split the packages to track separate release streams
Manually maintain these packages

## Problem Three packages (`openbao-plugin-secret-consul`, `openbao-plugin-secret-nomad`, `openbao-plugins`) all point to `github: openbao/openbao-plugins`. The latest release tag on that repo is `secrets-nomad-v0.1.5`, which is not a clean version string. `tools/update-gh` reports: ``` openbao-plugin-secret-consul: 0.1.0 -> secrets-nomad-v0.1.5 openbao-plugin-secret-nomad: 0.1.5 -> secrets-nomad-v0.1.5 openbao-plugins: 1.0.0 -> secrets-nomad-v0.1.5 ``` The tag `secrets-nomad-v0.1.5` appears to be a plugin-specific release tag, not a repo-wide release. Each package likely needs its own tag prefix filter. ## Options 1. Add a `tag_filter` field to metadata.yaml (e.g. `tag_filter: "secrets-consul-v"`) so `update-gh` queries the right release 2. Split the packages to track separate release streams 3. Manually maintain these packages

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unkin/rpmbuilder#117