Skip to content

v1.8.0

Choose a tag to compare

View all tags
@b10x-bot b10x-bot released this 13 Nov 13:44
· 41 commits to main since this release
v1.8.0
af10818

Since 1.7.0:

  • story:forge-access-anonymous: an instance mapping may name forge_access: anonymous. Its pod carries no credential of any forge and clones the public GitHub repositories its include entries name over HTTPS with none. The instance writes nothing to its forge (no push, pull request or comment) and reads no pull requests, issues, releases or workflow runs. Without the member nothing changes.

Known issue: with forge_access: anonymous, two kinds of daemon.kubernetes.env entries still reach the instance's pod: an entry under another name that names the same secret as a forge token variable (GH_TOKEN, GITLAB_TOKEN and the like), with that secret in the pod's Secret, and an entry GIT_CONFIG_GLOBAL or GIT_CONFIG_SYSTEM. Do not use the member with such a configuration before 1.8.1.

Upgrade: none. A daemon of an earlier release refuses a mapping with the member as an unknown key.

Container image

ghcr.io/beyond10x/conductor:1.8.0 at digest sha256:17df2aa4677c549ec05b608efdf9fb5e896c705832b4e25b044177e38d979cfc

docker run --rm ghcr.io/beyond10x/conductor:1.8.0 conductor --version
Assets 7
Loading