| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ci: T9047: dispatch docker-image rebuild against production ref
|
|
|
|
The Docker image rebuild curl-dispatch was still pointed at
vyos-reusable-workflows main, which is frozen pre-App-token-migration and
still uses the retired secrets.PAT checkout pattern (empty token, immediate
"could not read Username" auth failure on every dispatched run since
2026-06-02). The fix already shipped and is live on production
(VyOS-Networks/vyos-reusable-workflows#123, merged 2026-05-31) — this
caller was simply never repointed.
đŸ¤– Generated by [robots](https://vyos.io)
|
|
Build FIPS-compatible OpenSSL binaries
The FIPS provider does not get built and installed automatically.
To enable it, you need to configure OpenSSL using the `enable-fips` option.
|
|
Switch to "production" branch to call the package build workflow.
|
|
|
|
As salt has been marked deprecated via T8056 and is thus deprecated in VyOS 1.5
and VyOS 1.4 it is time to remove it from the rolling release.
|
|
|
|
(#1219)
|
|
|
|
|
|
Mergify ignore_conflicts:true already creates the backport workspace PR +
resolves toward theirs + applies backport-conflict for path-drift conflicts
(verified by canary VyOS-Networks/ipaddrcheck#26/#27). force_workspace's
'No backport have been created' trigger never fires under that config.
T8943 / IS-510.
|
|
Source-side wrapper (mirrored to the VyOS-Networks twin) for the public
vyos/.github force_workspace reusable. Inert on this public source (owner
guard); active on the mirror. force_workspace_enabled per-consumer (default false).
đŸ¤– Generated by [robots](https://vyos.io)
|
|
Adds the source-side LTS-name advisory caller (mirror-pipeline). Non-blocking;
posts a generic advisory if a PR title/body references a release-train branch name.
đŸ¤– Generated by [robots](https://vyos.io)
|
|
Mirror Pipeline Rollout 2 Task 6. Uniform canonical wrapper:
trigger branches [rolling, production], permissions: contents: read,
drop redundant wrapper-level MIRROR_ENABLED guard (now central).
đŸ¤– Generated by [robots](https://vyos.io)
|
|
* T8947: migrate remaining current→rolling residuals on rolling branch
Post-1c the default branch is `rolling`, but several build-config values
on this branch still referenced the old `current` repo path / codename /
train identity. These are not cosmetic — they break the rolling ISO build:
- docker/vyos-dev.list: apt source baked into vyos/vyos-build:rolling still
pointed at repositories/current (Hit/Err on package builds). Now
repositories/rolling + codename `rolling` (verified against live repo:
Suite/Codename `rolling`, Components `main`).
- data/defaults.toml: vyos_mirror → repositories/rolling; vyos_branch →
rolling (build-vyos-image checks out vyos-1x at this branch — `current`
no longer exists post-1c); release_train → rolling (apt pin codename +
os-release identity).
- data/live-build-config/archives/vyos-dev.pref.chroot: Pin codename
n=rolling to match the repo.
- data/versions: key current→rolling. build-vyos-image looks up
version_mapping[git_branch]; git_branch is `rolling`, so the `current`
key KeyErrored and the version fell back to 999.<timestamp>.
- .github/config/smoketest-branches.json: rolling-train entry key
current→rolling (looked up by branch name; was already 404ing on
rolling) + mirror + container_image to rolling.
os-release impact (intended): rolling images now report
VERSION_CODENAME=rolling and "(rolling)" in PRETTY_NAME/VERSION. The
-rolling version suffix is hardcoded and unaffected.
Companion to Rollout 1c (T8943). Ref IS-504.
đŸ¤– Generated by [robots](https://vyos.io)
* T8947: finish current→rolling residuals in docs/Dockerfile examples
Address adversarial-review findings (Codex) — stale current refs on the
rolling branch outside build config:
- .github/PULL_REQUEST_TEMPLATE.md: CONTRIBUTING link vyos-1x/blob/current
→ blob/rolling (was a broken link — vyos-1x renamed current→rolling in 1c).
- README.md: "Development Branches" section described the default branch as
`current`; updated to `rolling` (dropped the obsolete "may switch to main"
note — the rename already happened, to rolling).
- docker/Dockerfile: build-example comments vyos-build:current* →
vyos-build:rolling*.
Ref IS-504, companion to T8943.
đŸ¤– Generated by [robots](https://vyos.io)
|
|
Tracking: T8943
|
|
Rewrites uses: pins to the three HIGH-fanout producers (vyos/.github,
vyos/vyos-cla-signatures, VyOS-Networks/vyos-reusable-workflows) from their
old default branch to the new production compat branch staged in Task 1.
No functional change; pin-ref rewrite only.
Tracking: T8943
|
|
Replaces 5 caller workflows now superseded by central Mergify rules.
See https://vyos.dev/T8937 for the design + spec + plan.
Advances: T8937
đŸ¤– Generated by [robots](https://vyos.io)
|
|
(#1201)
Replace legacy per-secret caller with uniform stub that uses secrets: inherit
and vars.MIRROR_ENABLED opt-out. No functional change to trigger conditions.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1b-revised.md Task 5
đŸ¤– Generated by [robots](https://vyos.io)
|
|
|
|
|
|
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
|
|
|
|
general: T8595: add AGENTS.md
|
|
T8463: Update GitHub actions to latest versions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
T8219: Start building Salt from source
|
|
pull_request_targte policy update
|
|
|
|
policy change
|
|
|
|
|
|
updated label
|
|
|
|
|
|
T7748: Updated conflict reusable workflow reference in workflow
|
|
kea: T7281: Update Kea to 3.0
|
|
|
|
T75: remove pmacct
|
