https://github.com/vyos/vyos-build/pull/1236

https://github.com/vyos/vyos-1x/pull/5313

That is the test case bug introduced by PR 466
I will create a separate fix to the tests

2026-07-05 triage: keeping open, re-scoped. Since this was filed, most per-repo GHA was retired in favor of central Mergify automation (T8937), which shrank the fork-spam surface — but scheduled/cron workflows (e.g. CodeQL callers) still run on forks where jobs lack an owner guard. Remaining work = a fleet sweep adding if: github.repository_owner == 'vyos' (or the schedule-conditional variant) to jobs in scheduled workflows. Small, bounded; will be scheduled as an owner-guard sweep work item.

Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Overtaken by the 2026-05-30 default-branch rename (rollout 1c: 93 renames + ruleset-condition PATCHes) and the 2026-06-02 frozen current backport-alias restore (40 repos), which together resolved the fleet's branch-reference debt. No remaining actionable content identified on this task (empty description).

Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Delivered: the Mergify conflict check ships fleet-wide via the central baselines (vyos/mergify + VyOS-Networks/mergify, consumed by extends: on ~105 repos) — Label conflicting pull requests rule + conflicts merge-protection gate (T8615/T8935, shipped 2026-05-28).

Resolving in the 2026-07-05 stale-High triage (operator-confirmed). Delivered by later work: the custom/eps1lon conflict-check GHA was retired under T8937 (retirement closed 2026-06-12); conflict detection now runs via the central Mergify Label conflicting pull requests rule (T8615/T8935) plus the committed-marker script path (T8934). Nothing left to disable.

Related: https://vyos.dev/T8940

Why not use already existing prebuild FIPS edition of OpenSSL available in Debian?

According to:

Current kernel config available at:

Just guessing.

I want to have a 2nd opinion on that following this forum post:

Thank you for the clarification.

At least google AI tells me this:

Spent some time trying to chase this down. I managed to set up a VM to build the VyOS image, but I can't figure out how to build the kernel. The docs appear to be outdated?

Fix up as draft PR: https://github.com/vyos/vyos-1x/pull/5310

@natali-rs1985 You're right, looks like it's not being included in the package build! I'll investigate further, thanks!

@MattK Does your build include this patch?

Smoketests are failing:

https://github.com/vyos/vyos-1x/pull/5307

Fix PR: https://github.com/accel-ppp/accel-ppp-ng/pull/31/
(PR #30 was closed)

if you are asking about VyManager and VyMCP - I don't know them; it looks only two contributors at the moment...
My proposal here is structurally very different from their MCP implementation - I am proposing to add MCP capability into core VyOS, alongside with rest and GraphQL APIs we already have. They are essentially extending VyManager, that runs in 3 containers separate from VyOS

PR https://github.com/vyos/vyos-build/pull/1233

PR: https://github.com/vyos/vyos-build/pull/1232

PR for adding the missing documentation: https://github.com/vyos/vyos-documentation/pull/2124

Hi @mihakralj
Is it worth working on this given the community driven projects you mentioned?
I am learning MCP and deployment framework for them, and I am happy to help - as my learning effort

https://github.com/vyos/vyos-1x/pull/5305

New repository with PRs is here https://github.com/vyos/rest.vyos

s/set container \$container/set container name \$container/g

Proposed specs for implementation attached for review and discussion.
MCP Architecture proposal:

I noticed this independent VyMCP project just dropped a few hours ago. (there is no affiliation between this feature request and their implementation)

apologies, yes its a feature request. i must have fat fingered the category. can someone change it?

This reads a a core feature request, not exactly to do with Ansible Galaxy collection.
We can look into this from automation perspective once this feature is supported by the product

AI review revealed a bug when with ACTION state, the module also removes L2 configuration.
A module fix is required as such

1st, July, 2026: Contributor assistance is failing:

PR https://github.com/vyos/vyos-build/pull/1231

https://github.com/vyos/vyos-1x/pull/5304