| Age | Commit message (Collapse) | Author |
|---|
|
T9446: expose commit wait time for use in post-commit script.
|
|
In order to start the commit timer within the post-commit script
commit_revision, pass commit wait time in env var.
|
|
cstore: T9376: list tag values only when there is a tag limit to check
|
|
add_tag() read every existing value of the tag node, through the
session's unionfs, each time it added one, although the list is used
for nothing but the tag limit, and most tag nodes have none. Adding n
values was therefore O(n^2): on a 1.5.1 VM the boot-time load of a
config with a 10,000-rule prefix-list took 50 min 13 s (with the T9374
parser fix installed), and `load` of a 4,000-rule list 474 s.
List the values only when tlimit > 0, the only case that uses them.
With this change the same boot-time load took 37.4 s and the 4,000-rule
`load` 16.3 s.
|
|
vbash: T7575: Remove bash version constraints
|
|
T9144: add no-prompt option to commit-confirm
|
|
|
|
T9164: accept NOS-/VD- Jira keys in task-id check; pin NOS in coderabbit
|
|
VD tracker project renamed to NOS (2026-07) - PR titles and commit headlines
using the new NOS- key must stop being flagged invalid-task-id; legacy VD-
keys stay accepted, and CodeRabbit now resolves NOS alongside VD. Fleet
replication of canary vyos/vyos-1x#5379, whose adversarial review tightened
the regexes to ASCII [0-9] + literal-space separators.
🤖 Generated by [robots](https://vyos.io)
|
|
ci: T9047: skip CodeQL on mirror twins (Code Security not enabled on private org)
|
|
|
|
org)
|
|
(#149)
|
|
|
|
|
|
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)
|
|
T8943: ci: add lts-name-check advisory caller
|
|
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)
|
|
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
|
|
(#139)
Switches to secrets:inherit (no explicit PAT/REMOTE_OWNER) and adds
MIRROR_ENABLED kill-switch via vars. Behavior-neutral — same trigger
conditions, same reusable workflow target.
Plan: ~/.claude/plans/2026-05-26-mirror-rollout-1b-revised.md Task 5
🤖 Generated by [robots](https://vyos.io)
|
|
chore: T8937: retire Mergify-replaceable GHA caller workflows
|
|
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)
|
|
coderabbit: T8851: add .coderabbit.yaml for central-config inheritance
|
|
|
|
ci(mergify): upgrade configuration to current format
|
|
|
|
T8852: migrate .github/mergify.yml to extends: mergify
|
|
Replace the inline T8531 predecessor config with `extends: mergify`,
deferring to the per-org central baseline (vyos/mergify on the vyos
side, VyOS-Networks/mergify on the mirror).
The old config hardcoded `sender=@vyos/maintainers` in
`commands_restrictions`. The cross-org mirror pipeline replicates this
file byte-for-byte to VyOS-Networks/vyatta-cfg, where the team
reference is invalid (different org). Result: `@Mergifyio backport`
was rejected on every VyOS-Networks/vyatta-cfg mirror PR with
"Team @vyos/maintainers is not part of the organization VyOS-Networks"
— see VyOS-Networks/vyatta-cfg#33.
After this change, `extends: mergify` resolves to the per-org central
config on each side, picking up the correct Maintainers team
automatically.
Backport to circinus and sagitta after merge — those branches carry
the same legacy file.
🤖 Generated by [robots](https://vyos.io)
|
|
ci: T8834: remove SonarCloud workflow
|
|
🤖 Generated by robots (https://vyos.io)
|
|
general: T8595: add AGENTS.md
|
|
|
|
|
|
|
|
T8218: removed unqueue from mergify yaml as it is not supported
|
|
|
|
T8587: add u64 type support
|
|
|
|
This reverts commit 519e60e15ab52f887b87a5474fdebbd45063b567.
|
|
This reverts commit fc06449dd9a255353cf21e369d5e3f1e74e8188d.
|
|
- cli_def.l: reject out-of-range integer literals (errno==ERANGE) as a
syntax error instead of silently classifying them as u32.
- cli_new.c (val_cmp): unify u32/u64 comparison through strtoull() with
errno/end-pointer validation so unparseable operands are skipped
instead of silently compared as 0, and so mixed u32/u64 operands are
evaluated correctly via the 64-bit path.
- cli_new.c (cond_formats/cond_format_lens): replace the unused
INT64_TYPE entries with NULL/0 sentinels and a comment, since
INT64_TYPE is handled via its own branch in val_cmp(); this removes
a latent foot-gun where '%llu' would write 8 bytes into a 4-byte
unsigned int slot of left_parts[] if a future refactor routed
INT64_TYPE through the generic path.
- cli_new.c: introduce type compatibility helpers and apply them so
that a u32-magnitude value is accepted in a u64 (INT64_TYPE) context
(validate_value, char2val_notext) and so that comparisons between
u32 and u64 operands proceed (check_comp, val_cmp). The reverse
direction (u64-magnitude value into a u32 field) remains rejected to
preserve u32 range enforcement.
|
|
T8531: restrict Mergify commands to maintainers team
|
|
Mirror existing u32 handling to introduce a new u64 integer type:
- Add INT64_TYPE to vtw_type_e enum
- Register 'u64' type name and extend template lexer to classify
integer literals as INT64_TYPE when they exceed UINT_MAX
- Accept full u64 range in value lexer (strtoull / ULLONG_MAX)
- Add %llu cond_formats slot and INT64_TYPE comparison path in
val_cmp; map INT64_TYPE in type_to_name
- Add u64 / u64:* cases to bash completion value formatter
|
|
|
|
T8313: make copy/rename vyconf aware
|
|
|
