chore(dev): kill Ruby and port release scripts to native vdev (#25379)

* chore(dev): replace Ruby release flow with internal vdev functions

Ports the two remaining Ruby release scripts to native Rust and folds
the resulting `vdev release` surface down to the bits that are actually
called.

- `scripts/generate-release-cue.rb` (467 lines) is replaced by a
  `pub(super) fn run` in `vdev/src/commands/release/generate_cue.rs`.
  The function walks `git log v<last>...HEAD` (three-dot symmetric
  difference, so `--cherry-pick --right-only` filters out commits
  already released on a patch branch — the Ruby form), parses the
  conventional-commit messages, processes `changelog.d/*.md` fragments
  into the release CUE schema, and runs `cue fmt`. It is called only
  from `vdev release prepare` (no standalone CLI subcommand).

- `scripts/release-commit.rb`, `vdev release commit`, `vdev release push`,
  `vdev build release-cue`, and the corresponding Makefile targets
  (`make release`, `release-commit`, `release-push`) are removed: none
  of them were called by CI workflows, scripts, or issue templates, and
  the original `release-commit.rb` had been broken for some time
  (pointing at `docs/reference/releases`, a directory that no longer
  exists). Manual operator tagging happens via `git tag` directly per
  the release issue templates.

- The `scripts/util/*.rb` library, `Gemfile`, `Gemfile.lock`, and the
  `Gemfile` COPY in `scripts/environment/Dockerfile` are deleted.
  `ruby` itself stays in the bootstrap scripts and `vdev/README.md` —
  `scripts/check-events` is the last remaining Ruby script and gets
  ported in a follow-up commit.

- Docs, issue templates, the `changes.yml` workflow filter, and
  `website/README.md` are repointed at `cargo vdev release prepare`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(dev): port scripts/check-events to vdev via syn AST

Replaces the last Ruby script in the repo (515 lines) with a native
`vdev check events` that walks Rust source via `syn`'s AST instead of
regex-scraping. The validation rules from `docs/specs/instrumentation.md`
are preserved unchanged; behaviour against the current tree matches
the Ruby script (`0 error(s)` on master, identical reports on a
synthetic fixture exercising every rule branch).

Implementation notes:

- Structural scanning (struct fields, impl-block trait/event names)
  uses syn visitors. Macro argument parsing (`counter!(...)`,
  `trace!(...)`, etc.) uses small targeted regexes on the macro's
  already-tokenised input. Use-counting (`emit!(EventName)` /
  `register!(...)`) uses one regex pass over the raw source because
  syn does not descend into the bodies of opaque macros like
  `tokio::select!` where some emit sites live.

- `## skip check-validity-events ##` is added to
  `lib/vector-common/src/internal_event/component_events_dropped.rs`.
  That impl block is the foundation type the `registered_event!` macro
  abstracts over, so it has to implement `RegisterInternalEvent` by
  hand. The Ruby script's regex never matched its multi-line `impl`
  header and so silently let it through; the AST scanner sees it
  correctly and the existing skip-marker mechanism makes the intent
  explicit.

- `proc-macro2`, `quote`, and `syn` are declared as workspace deps with
  default-features off; vdev opts into the syn `full`, `visit`,
  `extra-traits`, `printing`, `parsing` features and proc-macro2's
  `span-locations` locally. These features are already pulled in
  transitively by Vector's existing dep graph (verified via
  `cargo tree -p vector`), so the additions do not change Vector's
  production binary.

- 32 unit tests are added: 14 covering the macro/log/metric arg
  parsers (literal-first, named-field, variable, trailing-literal,
  `%`-capture, message format checks, comma-arg nesting,
  `CamelCase → snake_case`) and 18 driving every branch of
  `validate_event` with synthetic `Event` structs.

- Differential test (run by hand against a worktree with a synthetic
  fixture file): `ruby scripts/check-events` and `cargo vdev check
  events` flagged the same eight events plus the same duplicate pair;
  outputs differed only in sort order and a Ruby string-escape
  artefact.

The bootstrap scripts (`scripts/environment/bootstrap-{macos,
ubuntu-24.04}.sh`), `vdev/README.md`, and `.ruby-version` lose their
Ruby references — there is no Ruby left in the repo to install.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(dev): make check-events robust to CWD and trailing-literal messages

Two bugs caught in code review of `vdev/src/commands/check/events.rs`:

1. The native check globbed `src/**/*.rs` and `lib/**/*.rs` relative to
   the caller's CWD. The Ruby script wrapper used to chdir to the repo
   root, so this silently regressed: running `vdev check events` from
   anywhere outside the repo root produced `0 error(s)` without
   scanning anything.

   Fix: chdir to `paths::find_repo_root()` at the top of `Cli::exec`,
   matching the previous wrapper's behaviour. Running from a subdir
   now scans correctly; running from outside the repo errors out with
   a useful message.

2. `parse_log_args` claimed the first bare positional expression as
   the log message before scanning the rest of the args for a string
   literal. For real Vector code that uses
   `warn!(%error, "Failed to flush.")`, the literal is the actual
   message but the function never reached it — so the message-format
   check (capital + trailing period) silently never fired on those
   sites.

   Fix: walk all args once, classify each as a literal candidate,
   `message =` named-field candidate, bare-positional candidate, or
   plain parameter, then pick the message in that priority order.
   Adds a regression test covering the bare-then-literal pattern.

Both bugs were flagged by Codex code review on PR #25379.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(dev): cover nested log calls and dedup against released metadata

Three review findings on the check-events / release-cue ports:

- `vdev check events` only ran its log-message format check via the
  syn AST visitor, which does not descend into the bodies of opaque
  outer macros like `tokio::select!` / `cfg_if!`. Log calls nested
  inside those macros were silently exempt. Replaces the AST format
  check with a raw-text pass that finds every `(trace|debug|info|
  warn|error)!(...)` invocation regardless of nesting. Adds two unit
  tests against the new pass — including one that asserts a violation
  inside a synthetic `tokio::select!` block is still reported.

- `generate_cue::run` no longer relies on `--cherry-pick --right-only`
  alone to dedupe commits against earlier releases — that flag only
  filters patch-id-equivalent commits, so a conflict-resolved cherry-
  pick (different SHA, same PR) could re-appear in the next release
  CUE. Adds a `collect_released_identifiers` pass that pulls the SHA
  and PR-number sets out of every existing
  `website/cue/reference/releases/*.cue`, then filters the fetched
  commit set against both. Two unit tests cover the extractor.

- `Commit::validate` now bails when the conventional-commit parser
  could not classify the subject (`type: None`). Previously such
  commits passed validation and landed in the published release CUE
  with a null type — a malformed PR title would silently ship.

Also factors `parse_log_args` so it shares one `&str` implementation
with the new raw-text pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(dev): apply rustfmt over previous fix

Pre-push hook reformatting on the format-check + dedup fixes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(dev): replace map().unwrap_or(false) in check-events test helper

`cargo clippy -p vdev --all-targets` flagged two map_unwrap_or lints
in the test-only `check()` helper. Identical pattern to fixes already
applied in production code; just missed when test cases were added
later.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(dev): clean up vdev check-events module

Drop the pedantic clippy allows the file was carrying and refactor to
satisfy them: rename Event fields whose `_event` suffix tripped
struct_field_names, group the three skip flags into a SkipFlags
substruct (struct_excessive_bools), and split validate_event and
Cli::exec into smaller helpers (too_many_lines).

Also remove a redundant `name_ends_with` wrapper that just called
str::ends_with, and merge the parse_log_args TokenStream wrapper into
its `&str` body. One callsite was already operating on stringified
tokens, so it was doing a wasted parse-and-restringify round trip.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(deps): use convert_case for snake-casing in vdev check-events

Replace the bespoke `camel_to_snake` regex helper in vdev's check-events
with `convert_case::Casing::to_case`. Promote convert_case to a
workspace dep so vdev and vector-config-common share the same version
declaration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore: drop outdated comment on workspace proc-macro2/quote/syn deps

The comment claimed declaring these at the workspace level prevented
vdev's extra `syn` features from unifying into Vector's production
build. That's not what workspace declarations do — `cargo` unifies
features across the resolved dep graph regardless. The reason vdev's
features don't reach the `vector` package is simply that vdev isn't a
dep of `vector`. The comment was also stale: these crates are now
direct deps of vector-config-macros, vector-config-common, and
vector-common-macros, not just vdev.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(dev): accept uppercase release scopes in conventional-commit parser

The release-CUE generator rejected commit subjects with uppercase scope
characters (e.g. `fix(ARC): ...`), even though `.github/workflows/semantic.yml`
explicitly lists `ARC` as a valid scope. A PR title that passed semantic
validation could therefore block `release prepare` later. Widen the
scope character class to allow uppercase letters and add a regression
test.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(dev): track angle brackets in macro-arg splitter

split_comma_args only tracked `()[]{}` nesting, so a registered_event!
handle field with a generic type containing a comma would be split
mid-type. The existing src/internal_events/filter.rs field
`Registered<ComponentEventsDropped<'static, INTENTIONAL>> = register!(...)`
broke before the assignment, hiding the register! emission and causing
spurious missing-log/counter errors for FilterEventsDropped.

Track angle depth as a separate counter and only decrement `>` when
there is a matching `<`, so the `>` in `key => value` tag pairs (used
inside counter! args) stays unaffected.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: pront

.github/ISSUE_TEMPLATE/minor-release.md

@@ -45,7 +45,7 @@ Automated steps include:
 - Pin VRL to latest released version rather than `main`
 - Check if there is a newer version of [Alpine](https://alpinelinux.org/releases/) or [Debian](https://www.debian.org/releases/) available to update the release images in
       `distribution/docker/`. Update if so.
-- Run `cargo vdev build release-cue` to generate a new cue file for the release
+- Generate a new cue file for the release in `website/cue/reference/releases/`
   - Copy VRL changelogs from the VRL version in the last Vector release as a new changelog entry
         ([example](https://github.com/vectordotdev/vector/blob/9c67bba358195f5018febca2f228dfcb2be794b5/website/cue/reference/releases/0.41.0.cue#L33-L64))
 - Update version number in `website/cue/reference/administration/interfaces/kubectl.cue`

.github/ISSUE_TEMPLATE/patch-release.md

@@ -24,8 +24,10 @@ export PREP_BRANCH=prepare-v-0-"${CURRENT_MINOR_VERSION}"-"${NEW_PATCH_VERSION}"
 - [ ] Cherry-pick in all commits to be released from the associated release milestone
   - If any merge conflicts occur, attempt to solve them and if needed enlist the aid of those familiar with the conflicting commits.
 - [ ] Bump the release number in the `Cargo.toml` to the current version number
-- [ ] Run `cargo vdev build release-cue` to generate a new cue file for the release
-  - [ ] Add description key to the generated cue file with a description of the release (see
+- [ ] Add a new cue file for the release at `website/cue/reference/releases/${NEW_VERSION}.cue`
+      by copying the previous patch release file and editing the version, date, commits, and
+      changelog entries to match this release.
+  - [ ] Add a description key to the cue file with a description of the release (see
         previous releases for examples).
 - [ ] Update version number in `distribution/install.sh`
 - [ ] Add new version to `website/cue/reference/versions.cue`

.github/workflows/changes.yml

@@ -228,7 +228,6 @@ jobs:
               - "vdev/**"
               - ".github/workflows/changes.yml"
             component_docs:
-              - 'scripts/generate-component-docs.rb'
               - "vdev/**"
               - 'website/cue/**/*.cue'
               - 'docs/generated/**'

.ruby-version

@@ -149,6 +149,7 @@ clap = { version = "4.5.60", default-features = false, features = ["derive", "er
 clap_complete = "4.5.66"
 colored = { version = "3.1.1", default-features = false }
 const-str = { version = "1.1.0", default-features = false }
+convert_case = { version = "0.8", default-features = false }
 criterion = "0.8"
 crossbeam-utils = { version = "0.8.21", default-features = false }
 darling = { version = "0.20.11", default-features = false, features = ["suggestions"] }
@@ -198,6 +199,9 @@ tokio = { version = "1.49.0", default-features = false }
 tokio-stream = { version = "0.1.18", default-features = false }
 tokio-test = "0.4.5"
 tokio-tungstenite = { version = "0.20.1", default-features = false }
+proc-macro2 = { version = "1", default-features = false }
+quote = { version = "1", default-features = false }
+syn = { version = "2", default-features = false }
 toml = { version = "0.9.8", default-features = false, features = ["serde", "display", "parse"] }
 tonic = { version = "0.11", default-features = false, features = ["transport", "codegen", "prost", "tls", "tls-roots", "gzip"] }
 tonic-build = { version = "0.11", default-features = false, features = ["transport", "prost"] }

Cargo.lock

@@ -595,13 +595,6 @@ package-%:
 
 ##@ Releasing
 
-.PHONY: release
-release: release-prepare generate release-commit ## Release a new Vector version
-
-.PHONY: release-commit
-release-commit: ## Commits release changes
-	@$(VDEV) release commit
-
 .PHONY: release-docker
 release-docker: ## Release to Docker Hub
 	@$(VDEV) release docker
@@ -618,10 +611,6 @@ release-homebrew: ## Release to vectordotdev Homebrew tap
 release-prepare: ## Prepares the release with metadata and highlights
 	@$(VDEV) release prepare
 
-.PHONY: release-push
-release-push: ## Push new Vector version
-	@$(VDEV) release push
-
 .PHONY: release-s3
 release-s3: ## Release artifacts to S3
 	@$(VDEV) release s3

Cargo.toml

@@ -147,9 +147,12 @@ watchexec "make check-docs"
 
 ### Changelog
 
-Contributors do not need to maintain a changelog. This is automatically generated
-via the `make release` command, made possible by the use of
-[conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) titles.
+Contributors document user-facing changes by adding a fragment under
+[`changelog.d/`](../changelog.d/README.md); the release CUE file's user-facing
+changelog section is assembled from those fragments by `cargo vdev release
+prepare` during release prep. The CUE file's `commits:` array is populated
+from the git log via [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/)
+titles, so PR titles must follow that spec.
 
 ### Release highlights
 

Makefile

@@ -27,9 +27,12 @@ impl<'a, const INTENTIONAL: bool> From<&'a str> for ComponentEventsDropped<'a, I
     }
 }
 
+// ComponentEventsDropped is the foundation type the `registered_event!` macro
+// abstracts over, so we have to implement RegisterInternalEvent by hand here.
 impl<'a, const INTENTIONAL: bool> RegisterInternalEvent
     for ComponentEventsDropped<'a, INTENTIONAL>
 {
+    // ## skip check-validity-events ##
     type Handle = DroppedHandle<'a, INTENTIONAL>;
     fn register(self) -> Self::Handle {
         Self::Handle {

docs/DOCUMENTING.md

@@ -5,7 +5,7 @@ edition = "2024"
 license = "MPL-2.0"
 
 [dependencies]
-convert_case = { version = "0.8", default-features = false }
+convert_case.workspace = true
 darling.workspace = true
 proc-macro2 = { version = "1.0", default-features = false }
 serde.workspace = true